BogoMips (from "bogus" and MIPS) is a crude measurement of CPU speed made by the Linux kernel when it boots to calibrate an internal busy-loop. An often-quoted definition of the term is "the number of million times per second a processor can do absolutely nothing". BogoMips is a value that can be used to verify whether the processor in question is in the proper range of similar processors, i.e. BogoMips represents a processor's clock frequency as well as the potentially present CPU cache. It is not usable for performance comparisons among different CPUs.

History

In 1993, Lars Wirzenius posted a Usenet message explaining the reasons for its introduction in the Linux kernel on comp.os.linux:

Proper BogoMips ratings

As a very approximate guide, the BogoMips can be pre-calculated by the following table. The given rating is typical for that CPU with the then current and applicable Linux version. The index is the ratio of "BogoMips per clock speed" for any CPU to the same for an Intel 386DX CPU, for comparison purposes. With the 2.2.14 Linux kernel, a caching setting of the CPU state was moved from behind to before the BogoMips calculation. Although the BogoMips algorithm itself wasn't changed, from that kernel onward the BogoMips rating for then current Pentium CPUs was twice that of the rating before the change. The changed BogoMips outcome had no effect on real processor performance. In a shell, BogoMips can be easily obtained by searching the cpuinfo file:

Computation of BogoMips

With kernel 2.6.x, BogoMips are implemented in the kernel source file. It computes the Linux kernel timing parameter (see jiffy) value. The explanation from source code: /* * A simple loop like

• while ( jiffies < start_jiffies+1)
• start = read_current_timer;
• will not do. As we don't really know whether jiffy switch
• happened first or timer_value was read first. And some asynchronous
• event can happen between these two events introducing errors in lpj.
• • So, we do * 1. pre_start <- When we are sure that jiffy switch hasn't happened
• 2. check jiffy switch
• 3. start <- timer value before or after jiffy switch
• 4. post_start <- When we are sure that jiffy switch has happened
• • Note, we don't know anything about order of 2 and 3.
• Now, by looking at post_start and pre_start difference, we can
• check whether any asynchronous event happened or not */ is used to implement (delay in microseconds) and (delay in nanoseconds) functions. These functions are needed by some drivers to wait for hardware. Note that a busy waiting technique is used, so the kernel is effectively blocked when executing / functions. For i386 architecture is implemented in as: equivalent to the following assembler code which can be rewritten to C-pseudocode Full and complete information and details about BogoMips, and hundreds of reference entries can be found in the (outdated) BogoMips mini-Howto.

Timer-based delays

In 2012, ARM contributed a new implementation allowing the system timer built into many ARMv7 CPUs to be used instead of a busy-wait loop. This implementation was released in Version 3.6 of the Linux kernel. Timer-based delays are more robust on systems that use frequency scaling to dynamically adjust the processor's speed at runtime, as values may not necessarily scale linearly. Also, since the timer frequency is known in advance, no calibration is needed at boot time. One side effect of this change is that the BogoMIPS value will reflect the timer frequency, not the CPU's core frequency. Typically the timer frequency is much lower than the processor's maximum frequency, and some users may be surprised to see an unusually low BogoMIPS value when comparing against systems that use traditional busy-wait loops.