5 ms·
The problem with the Mill is its not clear to me what advantage it can hope to seize over the behemoth which is Intel. If the market opens up enough to justify
by XorNot 10y ago
The problem with the Mill is its not clear to me what advantage it can hope to seize over the behemoth which is Intel. If the market opens up enough to justify new architectures, then it's also opening up enough to let Intel pivot into that space and unlike everyone else they own the fabs to do it.
- naasking 10y ago> The problem with the Mill is its not clear to me what advantage it can hope to seize over the behemoth which is Intel. If the Mill actually achieves the stated 10x improvement in performance per watt, you'd be quite stupid not to use it in highly competitive markets like smartphones, because others will. It would provide a significant competitive advantage.
- gilrain 10y agoYou would have thought the same about the SoC space, but they let it slip away. Intel does have the ability the squash competition, but it's not strategically perfect.
- gpderetta 10y agoThat's why the Mill team has been stockpiling patents for a while.
- peller 10y agoThis is drastically over-simplified, but in short, the Mill is a sort of middle-ground between superscalar implementations (x86, ARM) and VLIW (Itanium, DSPs). Superscalars leave a lot of the optimization process to complexity in the hardware. This is seen in stuff like the out-of-order scheduling and large cache hierarchies. In one of the Mill talks, it's guesstimated that almost 90% of the circuitry is dedicated to simply moving data around, as opposed to actually doing any work on that data. VLIWs take the opposite extreme, leaving the complexity of optimization to the compiler. History has shown so far though, that many computing problems are (again oversimplified) too conditionals-heavy to really benefit from VLIW, and end up running much more slowly. So the Mill is a bet that they can get more benefits from each approach without the major draw-backs of each. This isn't really ground Intel could simply "move into" without half a decade plus of work, and even then, they'd be cannibalizing their x86 ecosystem, which is not a risk most entrenched corporations are fond of.
- gpderetta 10y agoThe biggest issue with WLIW is the impredictability of the latency of memory loads which make any sort of static scheduling very hard for general purpose workloads. Itanium it seems had similar issues even with specialised hardware to help the compiler. Not sure what's the memory latency hiding story for the Mill. Edit: Symmetry said it better.
- MertsA 10y agoOn the Mill, you tell it the address that you want to read and when you want to read it. So you could issue a load for XYZ as soon as you know what XYZ is and if there's a subsequent store to XYZ that will update the result so when the load returns you have the data that was there when the load returns and not from when the load was issued. If you issue a load that completes in 5 cycles and it needs to go to RAM for that data then it's going to stall waiting for that data but because you can issue loads sooner than on other architectures you can sort of alleviate some of the problems with stalling on some load.
- gpderetta 10y agoBut as far as I understand and hear, Itanium had sort-of similar capabilities (ALAT and speculative loads) and it didn't work great outside of FP workloads as it is still hard to programmatically schedule load early even if you can ignore RAW hazards. What's unique in the Mill?
- Symmetry 10y agoBasically they've used their exposed pipeline design and register metadata to fix the things that didn't work well about ALAT. Or at least that's the theory. EDIT: I think the main problem was that on Itanium issuing a speculative load could potentially trigger a page fault making it potentially dangerous. On the Mill the page fault won't trigger until the load leads to a side effect outside the belt, sort of like it's been wrapped in a Haskell Maybe monad. So if you' have something like for (int i = 0; i < foo; i++) { a[i] = a[i]+1; } you can speculatively load the a[i+n] while you're working on a[i] even if allocated memory stops at the border of the array allocation.
- elihu 10y agoA couple things: 1) Intel is very heavily invested in x86, and they're likely to be very reluctant to change. 2) The Mill folks have patents, which might be hard to work around. 3) If the Mill becomes successful, they're likely to either be bought out by one of Intel's behomoth competitors, like Samsung or Qualcomm, or perhaps even by Intel itself. 4) If Intel really likes their technology, they could license it from Mill Computing. It would be surprising for Mill to say no to a reasonable offer, considering that they don't have their own fabs and it's their business model is to license their designs to those that do.
- igodard 10y agoAll but #4. Our business model is to sell chips, not licenses. Why? Intel's quarterly dividend is bigger than ARM's annual revenue. Licensing is a backup plan.
- elihu 10y agoAh, thanks for the clarification.
- warkdarrior 10y agoYou forgot: 5) Intel really likes their technology, but they do not want to license it so they decide to implement tweaks around the Mill patents.
- igodard 10y agoA more likely strategy for a major (not Intel specifically) is to just use whatever they want without a license, and beat us to death with lawyers.