Sockets, cores and threads, oh my
Intel's silicon brick roadmap
Intel gave us lucky hacks a post-Nehalem launch briefing to outline aspects of its near-term processor roadmap. Here's a fast-paced tour through the briefing content.
Intel reassured us that it could see Moore's Law progression being maintained for another ten or so years with the process shrinks and other developments in its roadmap. The inexorable rise in transistor counts on dies, 731 million with Nehalem quad-cores, should continue over that period. The big issue is people comprehending how to use parallelism.
Intel Server Processors
Intel's server platforms groups covers several markets: high-performance computing (HPC), internet data centres and the cloud, RISC migration, storage and the virtualised data centre. Its building blocks are CPUs, chipsets, the LAN, SSD/RAID, boards/KDKs and software. Its processor platforms are Itanium (9000 series) for mission-critical servers, Xeon 7000s for high-end enterprise servers, Xeon 5000s for mainstream enterprise quad- and dual-socket servers, and Xeon 3000s for single socket SME servers. Obviously Xeon 7000s and Itanium compete in everyone's eyes but Intel's.
Much was made of Intel designing in virtual server support features to hopefully get apps running in virtual machines running as fast as apps running in a non-virtualised server.
We had a quick romp through the Xeon 5500's features and then got to the interesting bit, Westmere-EP, the next-generation Nehalem (5000 series) processor built with a coming 32nm process. Westmere is basically a Nehalem shrink onto the 32nm process.
It will have six cores, cache enhancements and better energy efficiency, and will be announced in 2010. Also it will be socket-compatible with the 5500, so server vendors can use existing server boards and plug Westmere processors straight in. The graphic showed a PCI 2 bus linking Westmere to an Intel X25-E SSD, and an Intel 10GbitE controller.
Intel has a tick-tock analogy for its engineering developments. A "tick" is a process shrink using the current micro-architecture. The last tick was the move to the current 45nm process technology. A "tock" is the introduction of a new processor micro-archictecture and Nehalem is the latest tock event.
It will be followed by the 32nm tick which will, in turn, be followed by the next micro-architecture after Nehalem.
On the 7000 front the 7400 is a 6-core 45nm processor that's socket-compatible with the previous 7300. It will be followed by Nehalem-EX in the second half of this year and then Westmere-EX some time later.
Nehalem-EX, built on the 45nm process, is an 8-core processor designed for 4-socket platforms, meaning 64 threads (2 threads/core still). It will use an Intel Scalable Memory Interconnect with Buffers and what Intel called next-generation I/O technology with virtualisation.
There will be Intel VT technology in the processor (VT-x), the chipset (VT-d) and for the network (VT-c). The idea is to get these components working better together so that server vendors will go all-Intel instead of using third-party chipsets and communications interfaces. Thus there's no need for a Fibre Channel over Ethernet adapter, a CNA, because these VT features plus Intel's software FCOE initiator will get the Intel 10GbitE NIC spurting out FCOE packets at near wire speed to direct-attached devices.
There will be Virtual Machine Device Queues (VMDq) to improve throughput by offloading data sorting to the NIC. In a virtualised server the virtual machine (VM) will more or less talk directly to the NIC without having to go through the hypervisor. (Naturally that means the individual VMs in the server use CPU cycles to do the FCOE work though. Why Intel doesn't go for FCOE-offload is beyond me. It tried to do the same thing with TCP/IP offload, saying there was no need, and pretty much lost that argument.)
Intel has introduced Flex Migration so VMs can be readily transferred between different Xeon servers. Previously, notwithstanding instruction set compatibility between 3000s, 5000s and 7000 Xeons, VMs could only be moved between similar processor types.
We can expect a Nehalem version of the 3300, probably the 3400 and probably later this year or in 2010.
Sponsored: DevOps and continuous delivery