http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/ Engadget Comments for Intel's 6-core Xeon and Nehalem CPU info leaked http://www.engadget.com/media/feedlogo.gif http://www.engadget.com en-us Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:06PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:30PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:07PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
I don't believe this method is written in stone but the codenames do give a guide on what may be coming down the pipeline.]]>Feb 25th 2008 1:30PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
(unless I have missed some glaringly obvious compatibilty issue)]]>Feb 25th 2008 12:07PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Uh, yeah you did miss one little detail. These chips are socket 604 not socket 771 that the skulltrail uses.]]>Feb 25th 2008 1:04PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:34PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:10PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:13PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:26PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:07PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
I believe the time for Quad cores has come!]]>Feb 25th 2008 2:51PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:13PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:15PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Powered by Jesus

on my PC]]>Feb 25th 2008 12:25PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:07PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:19PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 6:29PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:30PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Eventually all programs will just have to design their code based on the criteria of a finite unknown number of cores. ]]>Feb 25th 2008 12:33PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Poor Amiga/Be. You would have been spectacular.]]>Feb 25th 2008 2:23PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Poor AMD if this ends up being true.


http://blogs.zdnet.com/Ou/?p=1025]]>Feb 25th 2008 12:33PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:33PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 27th 2008 9:51AMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 26th 2008 12:57PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
step back intel, we dont care how many cores there are just yet.
give us 3.5ghz the ability to address more than 3.5gb of ram in 32bit windows ( yes, i know im blaming the wrong people... i just dont know who to blame for that.. is it the kernel or the architecture? )

oh and Christ, does it take a rocket-scientist?
remember Pentium 4 HT ( hyper threading )?

cant you just un-hyper thread so the 2/4/6 cores appear as one and have the cpu delegate tasks?]]>Feb 25th 2008 12:35PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Second, 32bit can only reference that amount of memory. Its a limit at the size of address that can be stored in 32 bits. An OS maker can fake access, but why bother. Just switch to 64 as it has become alot more mainstream that it was when XP64 was released.

Third, the OS is now being built with multi cores in mind, so theres little need for Intel to take care of controlling access to 4 cores. As soon as you scale that up, then you start to run into bottlenecks. As soon as Graphics cores are introduced and a core carries graphics as well as integer/fp units within it, then embedded access and delegation controllers will be part of the chip, which is what the OS will communicate with. But we really dont need that now. There are not enough cores, nor are any programs built natively to work with a single core that delegates tasks.

Remember, the programs run on the Cell have to be written with that in mind.

]]>Feb 25th 2008 12:47PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/If youre linux dude just switch to 64 bits...
if you're mac? i really don't know and don't care, but there should be many people that will help you in here.

just google before you start sending useless posts about 32 bits architecture...it can only address 3.2gb ram cause of physical or mathematical facts period.]]>Feb 25th 2008 1:13PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 6:18PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Where as in a small number of cores, different cores could be completing different tasks (or different threads) at the same time; in the case with a high number of cores, they are almost guaranteed to be at some point trying to work with the same piece of data at the same time. Some of the novel solution is to have things like transactional memory.

So that is pretty much my "simplified but flawed" explanation as to why more cores may not always be better. In conclusion, they need changes to the hardware platform in regards to memory access in order to push for more cores on a die, which In my very wild guess is what Intel is trying to do when they try to implement an on-die memory controller. ]]>Feb 25th 2008 6:32PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
If you want to buy a PC, it makes a lot of sense to wait for Nehalem, which is why Intel is not spilling too many beans on it because they don't want sales of late Penryn versions to evaporate.]]>Feb 25th 2008 1:28PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:41PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
The Nehalems probably wont be 6 core initially.

And even if we dont need it, why not be a step ahead, if the cost isnt much more than a quad core?]]>Feb 25th 2008 12:49PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
The more cores there are (and the better written the software is), the less time we have to wait. The less time we have to wait, the more awesome stuff we can make.

Let's not forget that gamers aren't the only ones who use computers for more than just Firefox and iTunes.]]>Feb 25th 2008 1:28PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
They are... and they are putting more of those on the same die. So in a way... you are getting your way. It's just that your being forced to buy more of them.]]>Feb 25th 2008 2:27PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 27th 2008 2:00AMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 12:49PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
The Cell has a controller core with x number of small calculation cores.

The individual cores dont fetch for data, but are fed data.

These are 6 individual controller "like" cores. They can do their own thing, or can be programmed to work together.]]>Feb 25th 2008 12:51PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 1:11PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 2:41PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/]]>Feb 25th 2008 1:35PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Feb 25th 2008 3:16PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Nehalem is the name of a town and river on the north Oregon coast. Whether that figures into the reason for the code name, I do not know.]]>Feb 26th 2008 2:18AMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
Server virtualization!

Running 10+ virtual servers on a single box would suddenly became much more feasible. Now, if metaram will ever come out...

I run an E8400 on my game rig. Seriously, how many SLI/Crossfire GPUs would you need to not bottleneck a 6 core CPU?]]>Mar 4th 2008 10:40AMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/Mar 18th 2008 4:03PMhttp://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/http://www.engadget.com/2008/02/25/intels-6-core-xeon-and-nehalem-cpu-info-leaked/
look at Conroe for instance its a city in texas
merom another city
clovertown another city

Getting the picture yet??]]>May 24th 2008 1:11AM