'Bloomfield' is the CPU codename just like Yorkfield, Kentsfield, Wolfdale, etc.
Nehalem refers to the CPU architecture family like Penryn does to 45nm Core 2s.
Printable View
'Bloomfield' is the CPU codename just like Yorkfield, Kentsfield, Wolfdale, etc.
Nehalem refers to the CPU architecture family like Penryn does to 45nm Core 2s.
Isn't Penryn the 45 nm version of Merom ?Quote:
Originally Posted by bowman
AFAIK, the name of a micro-arch keeps being the same whatever the process is. And in case of Core 2, uarch is "Core 2", whatever the process / platform.
There are differences in the micro-arch of 45nm and 65nm Core2. Differences like those between Katmai, Coppermine and Tualatin/Willamette, Northwood and Prescott. Those generations of CPUs were branded as Pentium 3/Pentium4 CPUs but their architectures, although very similar, were different.
Conroe and Penryn have also very similar m-arch and are belonging to the same m-arch generation: Core2.
Conroe is a reference for the 65nm Core2 m-arch. Penryn is a reference for the 45nm Core2 m-arch.
At same time Conroe is also a codename for the desktop 65nm Core2 Duo E6xxx with 4MB/2MB(where 2MB are disabled out of total 4MB) L2, while Penryn is the codename for the mobile 45nm Core2 Duo CPUs.
Bloomfiled is a codename for the desktop 45nm Nehalem quadcore CPU, analogically like Yorkfield/Kentsfield is the codename for the desktop 45nm/65nm Core2 quadcore CPU
Yeah, but you're not going to call a 45nm version of it Merom or Conroe, you're going to call it Penryn. Same with the 32nm version of Nehalem, it'll be referred to as Westmere just like Intel does to avoid confusion.Quote:
Originally Posted by cpuz
65nm Core 2's were initially referred to as Merom (mobile version), Conroe came later.
Yeap, there's ...Quote:
Originally Posted by cpuz
Quote:
Originally Posted by savantu
1 stick of 2G DDR3-1066 ...
Can you read what is written on it ?
If we can program the PLL, we can try to o/c (I guess the BIOS has no option at all for that, does it ?)
Nope ... while Intel has unified their architecture across the 3 markets, they still give separate code names for each product. Merom, Conroe, and Woodcrest (Clovertown) was the 65 nm for mobile, desktop, and server (server quad) repectively... Penryn, Wolfdale, and Harpertown were the 45 nm tick version. Nehalem is not clear to me, perhaps server in this case, Bloomfield is the high end DT.Quote:
Originally Posted by Anemone
Jack
Clovertown/Tigerton -> Beckton
Harpertown -> Gainestown
Yorkfield -> Bloomfield
Kentsfield/low price Yorkfield -> Lynnfield
Allendale/Wolfdale -> Havendale
That's correct.Quote:
Originally Posted by bowman
The Nehalem code name is unique in that it applies to the overall microarchitecture that includes all the above products. Correct me if I'm wrong, but this is the first time in recent history where Intel has used a codename for a microarchitecture that did NOT also apply to a specific product.
Here's the comprehensive list of Nehalem product code-names...
http://members.shaw.ca/virtualrain/n...alem-chart.png
I'm not that familiar with Rightmark but it looks like there's something wrong with Rightmark's Max bandwidth then... it reports 12.8GB/s but a single stick of DDR3-1066 has peak theoretical bandwidth of 8.5GB/s.Quote:
Originally Posted by JCornell
The measured B/W of 5.6GB/s is actually not that great.
The R/W numbers could be influenced by cache.
Any chance of an Everest memory performance screen shot?
Yepp, 5.6GB looks like my 2.6GHz Northwood with DDR while it was overclocked to 3.36GHz IIRC. Hey if I didn't say it already, thank for the great info:up:Quote:
Originally Posted by virtualrain
It does apply to a specific product. As far as manufacturing is concerned, it is the codename for the product that eventually becomes either Bloomfield or Gainstown depending on how it's binned and eventually how it is treated prior to packaging. Some of them will have 1 quick path lane disabled and then become Bloomfield, others remain whole and become Gainstown.Quote:
Originally Posted by virtualrain
HMMM, would a bloomfield function in a Gainstown board if all that is different is that 1 quickpath channel is disabled or would the cpuid come into play as my guess is they have different CPUID's and the one for Bloomfield wouldn't be loaded into the Gainstown BIOS.Quote:
Originally Posted by Blauhung
Am I on the right track or way off?:D
We might have another BP6 on our hands..Quote:
Originally Posted by Movieman
Well maybe not in the same price range. :rofl:
Very helpful, thank you.Quote:
Originally Posted by virtualrain
Jack
Np... It's part of the Nehalem FAQ... http://www.nehalemnews.com/
:)
You reading this thread..? Nvidia isn't making a chipset for the Nehalem! *Dee dee dee*Quote:
Originally Posted by Anemone
With latest release CpuZ v1.46 :clap:
http://i245.photobucket.com/albums/g...alem/Fritz.jpg
===
Look how the Core Temp works with HT :)
http://i245.photobucket.com/albums/g...lem/Core12.jpg
...
Nice stuff JC... any chance of an Everest Memory Benchmark?
:D
Just like I already mentioned before, can't run everest / sisoft (HW/SW detection problem I guess) :shrug:Quote:
Originally Posted by virtualrain
Here's one for you to try..Quote:
Originally Posted by JCornell
Download BOINC, attach to a project, WCG will do..:rofl:
Then run the benchmark, it should do it automatically when installed for the first time
That will say a lot on what the cpu has for 'stones";)
This is for a windows 32 bits OS:
http://boinc.berkeley.edu/download.php
This is for a windows 64 bit OS:
http://boinc.berkeley.edu/download_all.php
Grab the one that is ver 5.10.45 if you have a 64 bit OS
Hey JC, when we can see some OC results? :).
Hm :), OC with default vcore? It is not dangerous with default ,-)...