Today it was noticed, without any fanfare from Intel, that Knights Mill information has been uploaded to Intel’s specification database ARK. There are three known SKUs so far, with up to 72 cores and a 320W TDP. The Xeon Phi 'Knights Mill' products are a new iteration on the older 'Knights Landing' family, with a silicon change for additional AVX-512 instructions. As far as we can tell, these parts will only be available as socketable hosts and not as PCIe add-in cards.

In Intel’s approach to AI and compute and the data center, according to their talk at Hot Chips earlier this year, has multiple solutions depending on the workload. The Xeon Scalable Platform is meant for the widest variety of workloads, Xeon Phi for parallel acceleration and AI training, FPGAs for deep learning inference efficiency and the Crest family with dedicated deep learning by design. Each segment has its own roadmap, and the Xeon Phi roadmap has been somewhat confusing of late.

Moving from the 45nm Knights Ferry in 2010, Intel released 22nm Knights Corner in 2012 and 14nm Knights Landing in 2016. Last year, Intel had a contract with the Argonne National Laboratory to build the Aurora supercomputer at using 10nm Knights Hill (KNH) by 2020, which was the original successor to Knights Landing, however the KNH project was officially scrapped last month (Nov 2017) for various reasons, some citing Intel’s delay in releasing 10nm silicon. Intel still intends to follow through with the Aurora contract by 2021, it should be noted.

The new successor to Knights Landing (KNL) is Knights Mill (KNM), which was detailed back at Hot Chips. For the most part, the KNL and KNM chips are almost identical in core counts, frequencies, 36 PCIe 3.0 lanes, using 16GB of high-bandwidth MCDRAM and having six DRAM channels, but KNM offers a small design tweak to allow for better utilization of its AVX-512 units through supporting new sets of AVX-512 instructions as well as a small amount of silicon redesign. For pure performance metrics, this change means that Knights Mill offers only half of the double-precision performance of Knights Landing, but up to 2x in single precision and 4x with variable precision.

Intel Xeon Phi x205 Family (Knights Mill)
  Cores Base Turbo L2 TDP DRAM TCASE
7295 72 / 288 1.50 GHz 1.60 GHz 36 MB 320W DDR4-2400 77ºC
7285 68 / 272 1.30 GHz 1.40 GHz 34 MB 250W DDR4-2400 72ºC
7235 64 / 256 1.30 GHz 1.40 GHz 32 MB 250W DDR4-2133 72ºC

The three parts are officially members of the Xeon Phi x205 family, and match their x200 family members where the product numbers align (eg 7290 and 7295). The 7295 has the most cores and threads, with a higher frequency, more total L2 cache, support for DDR4-2400 and the higher temperature support. The 7285 is the middle of the pack, while the low end 7235 gives up some memory support, with only up to DDR4-2133.

The previous generation parts had some integrated OmniPath fabric versions (such as the 7290F) which do not seem to have migrated over to Knights Mill yet, though could potentially in the future. Each of the parts are similar to KNL, using 36 tiles of two cores, all connected with the 2D mesh, and each tile sharing 1MB of L2 cache with one VPU per core. 

On the specification side, everything seems pretty much by the book for core counts and frequencies. The one number that stands out is the 320W for the Xeon Phi 7295. This is a high power consumption number for a socketed processor, and if my memory serves me correctly, this is the highest TDP ever assigned to an Intel socketed CPU. This isn't the highest for a socketed processor though - IBM quoted 300-350W for its z14 hardware earlier this year, although it can go up to 500W on consumer request. The reason for this dramatic increase in Intel’s TDP number (we suspect) is three-fold: one, to catch more processors off the production line into the relevant voltage/frequency window, and two, the new instructions offer better utilization of the silicon, and three: double-pumped execution.

AVX-512 Support Propogation by Various Intel CPUs
  Xeon, Core X General Xeon Phi  
Skylake-SP AVX512BW
AVX512DQ
AVX512VL
AVX512F
AVX512CD
AVX512ER
AVX512PF
Knights Landing
Cannon Lake AVX512VBMI
AVX512IFMA
AVX512_4FMAPS
AVX512_4VNNIW
Knights Mill
Ice Lake AVX512_VNNI
AVX512_VBMI2
AVX512_BITALG
AVX512+VAES
AVX512+GFNI
AVX512+VPCLMULQDQ
AVX512_VPOPCNTDQ
Source: Intel Architecture Instruction Set Extensions and Future Features Programming Reference (pages 12 and 13)

The two headline changes on instructions for the new parts revolve around support for Quad FMA (QFMA, or 4FMAPS) for 32-bit floating point, and Vector Neural Network Instructions (VNNI) for 16-bit integers. To do this required changing the execution ports on the core.

Previously each VPU per core would offer identical 512-bit interfaces to the AVX-512 unit, supporting single precision (SP) and double precision (DP) math, with any half-precision (HP) falling under an SP block. In the new design, the ports are asymmetrical: the SP/DP block is split into a separate DP and SP/VNNI blocks, with one DP block removed (likely due to the size of the SP/VNNI block). This is best shown in the diagram above, though it means that DP performance is halved (2 blocks to 1), but SP performance is doubled (2 blocks to 4) and VNNI performance is quadrupled (2 SP blocks to 4 HP blocks).

The QFMA implementation allows for sequential fused-multiply-add to accumulate over four sets of calculations with a single instruction. Technically this adds latency, so the calculation needs enough ILP to hide the latency, but offers a single target for the vector accumulator and allows packing together of 12 aligned cycles in DRAM. Each FMA takes about 3 cycles.

For VNNI, the core takes two 16-bit integer inputs to give one 32-bit integer output for a horizontal dot product operation. The reason for using integer math here is two-fold: one, it enables 31-bits of INT prevision vs 24-bits of mantissa in FP, but also because IEEE standards are easier to implement in INT math.

Support for these new instructions and the silicon redesign means two things: one, the decoder potentially can work less, with more math being packed into a single instruction, but also caters to what Intel thought was a bottleneck in AVX-512 utilization: not enough codes were using all the AVX-512 unit all the time. This is designed to help increase utilization, and therefore would increase power consumption.

The other part of the equation is double pumping the AVX-512 unit, ensuring that the unit is fed at all times while reducing decode power.

Overall the KNM core is looks almost identical to the KNL core, aside from the VPU port changes. It still decodes 2-ops per cycle but gives out-of-order execution with 72-inflight micro-ops. To hide a lot of the latency, 4-way hyperthreading is enabled, hence why a 64-core part gives 256 threads.


Our KNL 7210 Sample

Intel’s major partners already have Knights Mill available for customers, although list pricing is currently not in Intel's Price List. It’s interesting that the data being added to Intel’s ARK platform wasn’t accompanied by any announcement, and seems to be a low-key affair. 

Source: Wikichip on TwitterIntel ARK

Additional

Something we missed in our first look at the specifications. Over the older Knights Landing parts, the new Knights Mill parts also support Intel virtualization technologies, specifically VT-d, VT-x and EPT.

Related Reading

POST A COMMENT

75 Comments

View All Comments

  • mode_13h - Tuesday, December 19, 2017 - link

    I get the point of Knights Landing, as it's more of a generic HPC processor. But I think Knights Mill actually misses the boat. It just can't compete with GPUs. Intel's acquisition of Nervana and creation of a dedicated GPU computing group seems like an acknowledgment of that fact. Reply
  • HStewart - Tuesday, December 19, 2017 - link

    I think all Phi Processor is aim at something different than what most people like to think - it not designed to replace Xeon for general purpose server computing and not designed to replace GPU for graphics

    It would be interesting to have a performance comparison between Xeon, Phi, and Atom chips core performance. My guess is that the per core - performance will be in that order - but per core performance for ARM based servers would be lower than even Atom ( Cxxxx series ). GPU cores are different area especially related to computing.

    " It just can't compete with GPUs. Intel's acquisition of Nervana and creation of a dedicated GPU computing group seems like an acknowledgment of that fact."

    I don't think Phi was ever meant to compete with GPU. I think Intel is planning on using it technology together to improved it products - GPU for example will not be limited to just High End but eventually compute with NVidia gaming GPU.

    I believe a lot of there technology is used work on ideas that will later go to mainstream. Hyperthreading is one example and of course AVX and AVX-512 ( for sure ) is another. This might mean also that 4 Way Hyperthreading is coming to 10nm processors.
    Reply
  • mode_13h - Tuesday, December 19, 2017 - link

    I don't know where you get your information, but Intel straight out said that Knights Mill was targeted at deep learning. It's just a Knights Landing where they traded off some fp64 performance in order to optimize deep learning performance. This puts it squarely in competition with GPUs and more specialized neural network chips. Reply
  • HStewart - Tuesday, December 19, 2017 - link

    "I don't know where you get your information, but Intel straight out said that Knights Mill was targeted at deep learning."

    I never stated this. All I stated is that Intel uses such platform to research newer technology in other technology. Knight Landing was never designed to replace the GPU
    Reply
  • mode_13h - Tuesday, December 19, 2017 - link

    BTW, did you notice this uses Silvermont Atom cores? So, the hyperthreading they implemented for it cannot be re-purposed for general purpose. Even in Atoms, since the current/next generation of those is already newer (Golmont/Goldmont Plus).

    Your opinion to information ratio is too high. Please read more and post less.
    Reply
  • HStewart - Tuesday, December 19, 2017 - link

    "BTW, did you notice this uses Silvermont Atom cores?"

    Please review your facts - Phi chips do not use Silvermont Atom - nothing but this statement indicates this and Intel's Ark does not
    Reply
  • HStewart - Tuesday, December 19, 2017 - link

    WikiChip link did mention it - but no where in this article or from Intel did it mention Silvermont

    In Any case Silvermont does not have AVX-512 - it would be odd to say Atom has it - but Core series does not have except for X series.
    Reply
  • mode_13h - Tuesday, December 19, 2017 - link

    I'm glad to see that you've started your journey. Please seek out and read more... Reply
  • HStewart - Tuesday, December 19, 2017 - link

    Just for information, I found an erratum in 486SLC chip from IBM - it had cache inverted when jumping between 16 and 32 bit mode. This was about 25 years ago - I try to keep up with technologies but no way like I was then. I interview with Intel, but at that time they did not want assembly language developers. My only regret is often my words don't come out as much as I think - but I learn over the years of development that it best to get source from company that made the product and not the internet - because like everything including this statement, Internet is full opinion. Reply
  • lmcd - Tuesday, December 19, 2017 - link

    Congratulations on your position within the industry, and skepticism is healthy, but this is information that did in fact come directly from Intel. There are members of this board who regularly post unverified claims, and they normally are easily spotted. For the most part, everyone else is either posting verified claims or attaching appropriate disclaimers ("as far as I remember," etc). Reply

Log in

Don't have an account? Sign up now