Earlier quoted context omitted.
...which has 2.14 DMIPS/MHz = 1.027 BIPS (more than 1 instruction per nanosecond). Fast enough? (BTW, when I see "mhz" I assume this means "milli-Hertz". Similar when people say they have a 42b structure -- I see this as a 42-bit structure. If I wanted to communicate "42 byte structure" I'd abbreviate as "42B structure". Capitals used judiciously transmit meaning compactly.)
FWIW, I've seen capitalization issues in datasheets. When they're this ubiquitous, it's better to use it as an opportunity to apply number sense as a sort of FEC for verbal understanding. A 480 millihertz ARM doesn't really make sense (if you were running at those rates, you're in such a niche that it has ISA considerations where ARM isn't a great option anymore). Similarly a 42 bit structure on an ostensibly 8 bit m…
As for millihertz: sure it could make sense, if the design were fully static and one was watching (with eyeballs) some LEDs on control and address and status lines -- in fact, in many 'homebrew' computers, having a setting to allow seeing the sequencing of instruction execution is often a built-in feature.
MHz. B for Bytes. $B for Billions of Dollars (not "$BN") etc. Rules like this reduce our overall cognitive burden, when followed by all. That, in turn, makes us more efficient.