3 ms·
The flip side of "no fragmentation" is, there's no ARM core with hardware multithreading, and there won't be one until ARM decides to make one, which AFAIK may
by _yosefk 12y ago
The flip side of "no fragmentation" is, there's no ARM core with hardware multithreading, and there won't be one until ARM decides to make one, which AFAIK may well be "never". You can license a core with hardware multithreading if you need it - say, MIPS from Imagination - but the ISA won't be ARM-compatible. To the extent that ARM's "software ecosystem" is valuable, it's a pity nobody can make a multithreaded ARM-compatible core. Similarly for other features.
On the other hand, x86, which is "open" to all of Intel, AMD and VIA who reached a patent war stalemate, has the problem of incompatible instruction set extensions, as documented in "Stop the instruction set war": http://www.agner.org/optimize/blog/read.php?i=25 http://www.agner.org/optimize/blog/read.php?i=25
Which problem is worse is hard to decide.
- frankchn 12y agoNot sure about your first point. ARM does license out its architecture/ISA (i.e. for you to implement your own processor with an ARM instruction set) in addition to complete cores (Cortex-A57, etc...). This is how Apple and nVidia can design their own ARM-compatible chips (Apple A8/NVidia Tegra K1 "Denver") without relying on Cortex cores.