User talk:Aluvus

Notice: I will be out of town quite a bit over the coming days. I'll be back.

Articles you might like to edit, from SuggestBot

SuggestBot predicts that you will enjoy editing some of these articles. Have fun!

Stubs: Socket 370; Thermal Design Power; Cool'n'Quiet; Socket 7; Pentium 5; SpeedStep; Pentium Extreme Edition; Socket 3; Socket 479; Socket 939; AMD K10; Present sense impression; Socket 478; Socket 754; Party admission; Socket T; Recorded recollection; PC card; Socket 940

Cleanup: Scientific evidence; X86 assembly language; Pelswick
Merge: CPU socket; Clock rate; Virtualization Technology
Add Sources: Windows "Vienna"; Montvale (processor); Boston slang
Wikify: Albert C. Martin; Chico, California; Yorkshireisms
Expand: D-Link; Benjamin Franklin Institute of Technology; Religious cosmology

SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. Your contributions make Wikipedia better -- thanks for helping.

If you have feedback on how to make SuggestBot better, please tell me on SuggestBot's talk page. Thanks from ForteTuba, SuggestBot's caretaker.

P.S. You received these suggestions because your name was listed on the SuggestBot request page. If this was in error, sorry about the confusion. -- SuggestBot 23:33, 10 June 2006 (UTC)[reply]

Core 2 Duo

Your first reference for Merom being out was the page for the announcement of the Core 2 brand, not for the Core 2 processors themselves. (Note that it speaks of Core 2 in the future tense - "When launched later this year, the Intel® Core™2 Duo processor will provide enhanced performance and energy-efficiency in mobile applications while bringing for the first time the benefits of energy-efficient performance to mainstream desktop computing.")

The Core 2 Duo specifications page lists only the E series, not the T series. Perhaps Intel has officially released Merom, and they haven't updated their Web site yet, but if nothing shows up there in the next few days, that would appear to suggest that they haven't announced Merom yet. Guy Harris 18:26, 27 July 2006 (UTC)[reply]

Note also that the Intel desktop processor roadmap page lists Core 2 (and the server roadmap and workstation roadmap pages list the Core Microarchitecture Xeon 5100 series), but their laptop roadmap page doesn't. Guy Harris 18:43, 27 July 2006 (UTC)[reply]

However, Intel's press release about the announcement speaks of the T series. I've no idea why the main Core 2 pages don't mention them. Guy Harris 00:21, 28 July 2006 (UTC)[reply]

Article in need of cleanup - please assist if you can

The article AMD K10, to which you have helped contribute, has been flagged as requiring cleanup.

If possible, we would appreciate your assistance in cleaning up this article to bring it up to Wikipedia's quality standards. If you are unsure what the nature of the problem is, please discuss this on the article's talk page.
If you do not want to receive bot-generated messages on your talk page, please consider using the nobots template on your user talk page

RAID Diagrams

Hi Alex,

Firstly I'd like to thank you for the diagrams you created for the RAID article - they really help get the point across and in this case the pictures (to me) say more than a thousand words. However, in that same article there are still (or again.. not sure) ASCII diagrams, which are much harder to interpret. I've considered following your footsteps and make images for those as well, so as to keep the article consistent. However, such images would probably not match the style of your images exactly.

Would it be possible for you to either create images for those other ASCII-diagrams as well, make public the method you used to create the diagrams or release the source files for the diagrams (Visio files or something like that?).. I'm sure the many wikipedians working on the article would appreciate it.

Kind regards,
Kander 22:05, 11 December 2006 (UTC)[reply]

Ascii art?

I see you do some work on fixing ascii art? Check out the page on ladder logic. Not that it's really worth updating... --ninjayeti

Re: Please do not destroy old conversations

Thanks for the hints but I already know about such methods, however so far there hasn't been anything worth keeping "long term" on my talk page using the methods you suggest. Certainly the recent comments by a certain user are more like stalking so that's why I removed them, the user was subsequently 3RR blocked. The history of the page is a good enough archive so far. At this point I will point you towards this diff and discussion [1] Fnagaton 09:38, 9 May 2007 (UTC)[reply]

One man's rubbish is another man's treasure. ;) I prefer to keep my talk page clean and tidy. Fnagaton 10:15, 9 May 2007 (UTC)[reply]

reverts

Sorry about that re-appearing template. My fault. Tony 07:02, 18 August 2007 (UTC)[reply]

No need to apologize. The page has just been very.... active... lately, and such things will happen. Hopefully everyone will be a bit more careful going forward. And hopefully you won't have need to keep reverting so many things. — Aluvus t/c 08:48, 18 August 2007 (UTC)[reply]

good catch!

Thanks for fixing my mis-revert on motherboard. The vandals there are starting to get to me it seems :-) ǝɹʎℲxoɯ (contrib) 20:48, 26 October 2007 (UTC)[reply]

October 2007

Hello. Regarding the recent revert you made to Motherboard: You may already know about them, but you might find Wikipedia:Template messages/User talk namespace useful. After a revert, these can be placed on the user's talk page to let them know you considered their edit was inappropriate, and also direct new users towards the sandbox. They can also be used to give a stern warning to a vandal when they've been previously warned. Thank you. richi 13:51, 29 October 2007 (UTC)[reply]

RE: Probable mistake

You probably have my talk page on your watchlist, but just in case, I'll point out my reply. Cheers! Tuvok[^T@lk/_{Improve me}] 06:56, 15 December 2007 (UTC)[reply]

Once again. :) Now I'm off to sleep; no more replies 'til tomorrow, I swear. Tuvok[^T@lk/_{Improve me}] 07:50, 15 December 2007 (UTC)[reply]

Talk:MOSNUM: {{delimitnum}} template

I just wanted to make you aware that I made a post here on Talk:MOSNUM regarding the new {{delimitnum}} template. See you there. Greg L (my talk) 22:14, 14 March 2008 (UTC)[reply]

Re: Possible error in browser timeline

Thanks for that information, I've just updated the image. ADeveria (talk) 13:51, 31 March 2008 (UTC)[reply]

Greg L RFC

I've started Wikipedia:Requests for comment/Greg L, listing you as one of those who tried to resolve the dispute. — Omegatron (talk) 01:49, 4 June 2008 (UTC)[reply]

Hello. I would appreciate your comments here and here. Thank you. Thunderbird2 (talk) 18:26, 15 June 2008 (UTC)[reply]

About mode of execution trace cache

If you remove my link again, I am reporting you to an admin, and I am not joking. You don't even understand how the L1 Trace works, many of Wikipedia are allowed to have external links, historic data. See Instructions per second for example and citation and some of them even have terms.

Plus you don't even understand how the modes of execution trace caches works, they are cahces able programmable by assembly / macros code, the links provide the types of mode that can be supported depending on the content of macros code. Also associtivity is directly related to execution trace caceh, it is the mechanism of using TLB & decoder to descript the code into readable machine code thus storing it into the execution trace caches, without this process execution trace caches is useless, I don't need to provide citation because I am not writing only to show what this topic is about, which you are not understanding, I am not currently planning on writing this into anything major / minor in the Netburst (microarchitecture) article. --Ramu50 (talk) 23:27, 20 July 2008 (UTC)[reply]

I am not sure how you have determined what I do or do not know about anything. The link that you are attempting to insert into NetBurst is a general article about cache associativity. It makes no mention of, and has nothing specifically to do with, trace cache. It has to do with processor cache in general, much like the article CPU cache (which already includes a section on associativity). The point of external links is to provide relevant information that is not suitable (for whatever reason) for inclusion into a Wikipedia article. The information covered in the link you have attempted to insert is already contained in the appropriate Wikipedia article. There is no compelling reason to include the external link in NetBurst. I removed your link for this reason, not as some general protest against external links.

Making threats about "reporting someone to an admin" is neither productive nor wise; it comes across as bullying, and assuming that you were to make such a report, little would come of it. You would have a hard time finding an admin that would admonish me for following Wikipedia:External links and providing detailed explanations for my actions. — Aluvus t/c 01:53, 21 July 2008 (UTC)[reply]

First you remove it without any legitimate reasoning therefore it is consider a form of vandalism. I was placing link to express a similar intention as See Also, which usually connotate the purpose of letting others learn topics that are relevant. The purpose of the execution trace cache link was to allow further understanding of trace cache. Because, currently in Wikipedia nobody has proven there wasn't any evidence that states Netburst architecture had the same or different design architecture of execution trace cache, I felt people should have the options of choosing to learn that info or not without the need of learning the entire CPU cache. (Because not everybody may have interest in such as a broad topic that deals with all types of CPU caches.)

Simply saying it is irrelevant without any explanation or legitmate reasoning in the edit summary of article's history is not accepted. I am only reminding you not to do it again, not as a threat. If it was a threat I wouldn't have use that vague tone of voice of writing. --Ramu50 (talk) 20:15, 21 July 2008 (UTC)[reply]

LGA 775

Discussion you stated earlier state the move from Socket 775 to LGA775 not LGA 755. Also my attempt to move the page using the move feature earlier ended in an error. Illegal Operation (talk)

xeon die size

Thanks for that cite. Of course my math was wrong (missed a decimal place) so it's about 22mm on a side, not 70mm. That is still really enormous, though not unbelievable. A die photo would be way cool. 67.117.147.249 (talk) 00:36, 20 July 2009 (UTC)[reply]

Intel has provided a large (5 MB) die shot here: http://download.intel.com/pressroom/images/Dunnington.jpg — Aluvus t/c 02:15, 20 July 2009 (UTC)[reply]

Link color CSS script for Vector

Hi Aluvus. Nearly three years ago, you gave very useful advice at [2] on how to change link colors using one's stylesheet. Very soon, Wikipedia will be switching its default skin from Monobook to Vector, and the linking color fix does not work for the latter. Do you know how to fix it? Thanks, Dabomb87 (talk) 00:38, 7 April 2010 (UTC)[reply]

I would expect a variant of the same method to work, but proper testing requires me to switch to the beta skin. I'm a little concerned that switching back (in the fairly likely event it breaks something in Opera) will not be easy; do you happen to know? — Aluvus t/c 03:56, 7 April 2010 (UTC)[reply]