Binary prefix

From Infogalactic: the planetary knowledge core
(Redirected from Mebi (binary prefix))
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Prefixes for multiples of
bits (b) or bytes (B)
Decimal
Value SI
1000 k kilo
10002 M mega
10003 G giga
10004 T tera
10005 P peta
10006 E exa
10007 Z zetta
10008 Y yotta
Binary
Value IEC JEDEC
1024 Ki kibi K kilo
10242 Mi mebi M mega
10243 Gi gibi G giga
10244 Ti tebi
10245 Pi pebi
10246 Ei exbi
10247 Zi zebi
10248 Yi yobi

A binary prefix is a prefix attached before a unit symbol to multiply it by a power of 2. In computing, such a prefix is seen in combination with a unit of information (bit, byte, etc.), to indicate a power of 1024.

The computer industry has historically used the units kilobyte, megabyte, and gigabyte, and the corresponding symbols KB, MB, and GB, in at least two slightly different measurement systems. In citations of main memory (RAM) capacity, gigabyte customarily means 1073741824 bytes. As this is the third power of 1024, and 1024 is a power of two (210), this usage is referred to as a binary prefix.

In most other contexts, the industry uses the multipliers kilo, mega, giga, etc., in a manner consistent with their meaning in the International System of Units (SI), namely as powers of 1000. For example, a 500 gigabyte hard disk holds 500000000000 bytes, and a 100-megabit-per-second Ethernet connection transfers data at 100000000 bit/s. In contrast with the binary prefix usage, this use is described as a decimal prefix, as 1000 is a power of 10 (103).

The use of the same unit prefixes with two different meanings has caused confusion. Starting around 1998, the International Electrotechnical Commission (IEC) and several other standards and trade organizations addressed the ambiguity by publishing standards and recommendations for a set of binary prefixes that refer exclusively to powers of 1024. Accordingly, the US National Institute of Standards and Technology (NIST) requires that SI prefixes only be used in the decimal sense:[1] kilobyte and megabyte denote one thousand bytes and one million bytes respectively (consistent with SI), while new terms such as kibibyte, mebibyte and gibibyte, having the symbols KiB, MiB, and GiB, denote 1024 bytes, 1048576 bytes, and 1073741824 bytes, respectively.[2] In 2008, the IEC prefixes were incorporated into the IEC 80000-13 standard.

History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main memory

Early computers used one of two addressing methods to access the system memory; binary (base 2) or decimal (base 10).[3] For example, the IBM 701 (1952) used binary and could address 2048 words of 36 bits each, while the IBM 702 (1953) used decimal and could address ten thousand 7-bit words.

By the mid-1960s, binary addressing had become the standard architecture in most computer designs, and main memory sizes were most commonly powers of two. This is the most natural configuration for memory, as all combinations of their address lines map to a valid address, allowing easy aggregation into a larger block of memory with contiguous addresses.

Early computer system documentation would specify the memory size with an exact number such as 4096, 8192, or 16384 words of storage. These are all powers of two, and furthermore are small multiples of 210, or 1024. As storage capacities increased, several different methods were developed to abbreviate these quantities.

The method most commonly used today uses prefixes such as kilo, mega, giga, and corresponding symbols K, M, and G, which the computer industry originally adopted from the metric system. The prefixes kilo- and mega-, meaning 1000 and 1000000 respectively, were commonly used in the electronics industry before World War II.[4] Along with giga- or G-, meaning 1000000000, they are now known as SI prefixes[defn. 1] after the International System of Units (SI), introduced in 1960 to formalize aspects of the metric system. (Note that K is the SI unit for temperature (kelvin) and should not be confused with k, the SI prefix for kilo.)

The International System of Units does not define units for digital information but notes that the SI prefixes may be applied outside the contexts where base units or derived units would be used. But as computer main memory in a binary-addressed system is manufactured in sizes that were easily expressed as multiples of 1024, kilobyte, when applied to computer memory, came to be used to mean 1024 bytes instead of 1000. This usage is not consistent with the SI. Compliance with the SI requires that the prefixes take their 1000-based meaning, and cannot be used as placeholders for other numbers, like 1024.[5]

The use of K in the binary sense as in a "32K core" meaning 32 × 1024 words, i.e., 32768 words, can be found as early as 1959.[6][7] Gene Amdahl's seminal 1964 article on IBM System/360 used "1K" to mean 1024.[8] This style was used by other computer vendors, the CDC 7600 System Description (1968) made extensive use of K as 1024.[9] Thus the first binary prefix was born.[defn. 2]

Another style was to truncate the last three digits and append K, essentially using K as a decimal prefix[defn. 3] similar to SI, but always truncating to the next lower whole number instead of rounding to the nearest. The exact values 32768 words, 65536 words and 131072 words would then be described as "32K", "65K" and "131K".[10] (If these values had been rounded to nearest they would have become 33K, 66K, and 131K, respectively.) This style was used from about 1965 to 1975.

These two styles (K = 1024 and truncation) were used loosely around the same time, sometimes by the same company. In discussions of binary-addressed memories, the exact size was evident from context. (For memory sizes of "41K" and below, there is no difference between the two styles.) The HP 21MX real-time computer (1974) denoted 196608 (which is 192×1024) as "196K" and 1048576 as "1M",[11] while the HP 3000 business computer (1973) could have "64K", "96K", or "128K" bytes of memory.[12]

The "truncation" method gradually waned. Capitalization of the letter K became the de facto standard for binary notation, although this could not be extended to higher powers, and use of the lowercase k did persist.[13][14][15] Nevertheless, the practice of using the SI-inspired "kilo" to indicate 1024 was later extended to "megabyte" meaning 10242 (1048576) bytes, and later "gigabyte" for 10243 (1073741824) bytes. For example, a "512 megabyte" RAM module is 512×10242 bytes (512 × 1048576, or 536870912), rather than 512000000.

The symbols Kbit, Kbyte, Mbit and Mbyte started to be used as "binary units"—"bit" or "byte" with a multiplier that is a power of 1024—in the early 1970s.[16] For a time, memory capacities were often expressed in K, even when M could have been used: The IBM System/370 Model 158 brochure (1972) had the following: "Real storage capacity is available in 512K increments ranging from 512K to 2,048K bytes."[17]

Megabyte was used to describe the 22-bit addressing of DEC PDP-11/70 (1975)[18] and gigabyte the 30-bit addressing DEC VAX-11/780 (1977).

In 1998, the International Electrotechnical Commission IEC introduced the binary prefixes kibi, mebi, gibi ... to mean 1024, 10242, 10243 etc., so that 1048576 bytes could be referred to unambiguously as 1 mebibyte. The IEC prefixes were defined for use alongside the International System of Quantities (ISQ) in 2009.

Disk drives

The disk drive industry followed a different pattern. Industry practice, more thoroughly documented at Timeline of binary prefixes and continuing today, is to specify hard drives using SI prefixes and symbols in their SI or "decimal" interpretation. Unlike binary-addressed computer main memory, there is nothing in a disk drive that influences it to have a total capacity easily expressed using a power of 1024. The first commercially sold disk drive, the IBM 350, had 50 (not 32 or 64) physical disk "platters" containing a total of 50,000 sectors of 100 characters each, for a total quoted capacity of "5 million characters."[19] It was introduced in September 1956.

In the 1960s most disk drives used IBM's variable block length format (called Count Key Data or "CKD").[20] Any block size could be specified up to the maximum track length. Since the block headers occupied space, the usable capacity of the drive was dependent on the block size. Blocks ("records" in IBM's terminology) of 88, 96, 880 and 960 were often used because they related to the fixed block size of punch cards. The drive capacity was usually stated under conditions of full track record blocking. For example, the 100-megabyte 3336 disk pack only achieved that capacity with a full track block size of 13,030 bytes.

Hard disk drive manufacturers used "megabytes" or "MB", meaning 106 bytes, to characterize their products as early as 1974.[21] By 1977, in its first edition, Disk/Trend, a leading hard disk drive industry marketing consultancy segmented the industry according to MBs (decimal sense) of capacity.[22]

One of the earliest hard disk drives in personal computing history, the Seagate ST-412, was specified as "Formatted: 10.0 Megabytes".[23] The specification of 4 heads or active surfaces (tracks per cylinder), 306 cylinders and when formatted with a sector size of 256 bytes and 32 sectors/track results in a capacity of 10027008 bytes. This drive was one of several types installed into the IBM PC/XT[24] and extensively advertised and reported as a "10 MB" (formatted) hard disk drive.[25] Operating systems and programs using the customary binary prefixes[defn. 4] show this as "9.5625 MB".

The hard drive industry continues to use decimal prefixes for drive capacity. Today, for example, a "300 GB" hard drive offers slightly more than 300×109, or 300000000000, bytes, not 300 × 230 (which would be about 322×109). Operating systems such as Microsoft Windows that display hard drive sizes using the customary binary prefix "GB" (as it is used for RAM) would display this as "279.4 GB" (meaning 279.4 × 10243 bytes, or 279.4 × 1073741824 B). On the other hand, Mac OS X has since version 10.6 shown hard drive size using decimal prefixes (thus matching the drive makers' packaging). (Previous versions of Mac OS used binary prefixes.)

However, other usages still occur. For example, in one document, Seagate specifies data transfer rates of some of its hard drives in both IEC and decimal units.[26] "Advanced Format" drives using 4096-byte sectors are described as having "4K sectors."[27]

Information transfer and clock rates

Like the hard drive, there is nothing in a computer clock circuit or data transfer path that demands or even encourages that things happen at rates easily expressed using powers of 1024, or even using powers of 2.

Computer clock frequencies are always quoted using SI prefixes in their decimal sense. For example, the internal clock frequency of the original IBM PC was 4.77 MHz, that is, 4770000 Hz.

Similarly, digital information transfer rates are mostly quoted using decimal prefixes:

  • The ATA-100 disk interface refers to 100000000 bytes per second
  • A "56K" modem refers to 56000 bits per second
  • SATA-2 has a raw bit rate of 3 Gbit/s = 3000000000 bits per second
  • PC2-6400 RAM transfers 6400000000 bytes per second
  • Firewire 800 has a raw rate of 800000000 bits per second
  • As of 2011, Seagate specifies the transfer speed of some hard disk drives with IEC binary prefixes as well as decimal.[26]

Standardization of dual definitions

By the mid-1970s it was common to see K meaning 1024 and the occasional M meaning 1048576 for words or bytes of main memory (RAM) while K and M were commonly used with their decimal meaning for disk storage. In the 1980s, as capacities of both types of devices increased, the SI prefix G, with SI meaning, was commonly applied to disk storage, while M in its binary meaning, became common for computer memory. In the 1990s, the prefix G, in its binary meaning, became commonly used for computer memory capacity. The first terabyte (SI prefix, 1000000000000 bytes) hard disk drive was introduced in 2007.[28]

The dual usage of the kilo, mega, and giga prefixes and their corresponding symbols K, M, and G as both powers of 1000 and powers of 1024 was recorded in standards and dictionaries. For example, the 1986 ANSI/IEEE Std 1084-1986[29] defined dual uses for kilo and mega.

<templatestyles src="Template:Blockquote/styles.css" />

kilo (K). (1) A prefix indicating 1000. (2) In statements involving size of computer storage, a prefix indicating 210, or 1024.

mega (M). (1) A prefix indicating one million. (2) In statements involving size of computer storage, a prefix indicating 220, or 1048576.

The binary units Kbyte and Mbyte were formally defined in ANSI/IEEE Std 1212-1991.[30]

Many dictionaries have noted the practice of using traditional prefixes to indicate binary multiples.[31][32] Oxford online dictionary defines, for example, megabyte as: "Computing: a unit of information equal to one million or (strictly) 1048576 bytes."[33]

The units Kbyte, Mbyte, and Gbyte are found in the trade press and in IEEE journals. Gigabyte was formally defined in IEEE Std 610.10-1994 as either 1000000000 or 230 bytes.[34] Kilobyte, Kbyte, and KB are equivalent units and all are defined in the obsolete standard, IEEE 100-2000.[35] Byte multiples using powers of 1000 up to yottabyte are given by the on-line computing dictionary FOLDOC (Free On-Line Dictionary of Computing).[36]

The hardware industry has coped with the dual definitions because of relative consistency: system memory (RAM) typically uses the binary meaning while magnetic disk storage uses the SI meaning. There are, however, exceptions and special cases. Diskettes use yet another "megabyte" equal to 1024×1000 bytes.[37] In optical disks, Compact Disks use MB to mean 10242 bytes while DVDs use GB to mean 10003 bytes.[38][39]

Inconsistent use of units

Deviation between powers of 1024 and powers of 1000

Computer storage has become cheaper per unit and thereby larger, by many orders of magnitude since "K" was first used to mean 1024. Because both the SI and "binary" meanings of kilo, mega, etc., are based on powers of 1000 or 1024 rather than simple multiples, the difference between 1M "binary" and 1M "decimal" is proportionally larger than that between 1K "binary" and 1k "decimal," and so on up the scale. The relative difference between the values in the binary and decimal interpretations increases, when using the SI prefixes as the base, from 2.4% for kilo to nearly 21% for the yotta prefix.

Linear-log graph of percentage of the difference between decimal and binary interpretations of the unit prefixes versus the storage size.
Prefix Binary ÷ Decimal Decimal ÷ Binary
kilo 1.024   (+2.4%)
 
0.9766   (−2.3%)
 
mega 1.049   (+4.9%)
 
0.9537   (−4.6%)
 
giga 1.074   (+7.4%)
 
0.9313   (−6.9%)
 
tera 1.100 (+10.0%)
 
0.9095   (−9.1%)
 
peta 1.126 (+12.6%)
 
0.8882 (−11.2%)
 
exa 1.153 (+15.3%)
 
0.8674 (−13.3%)
 
zetta 1.181 (+18.1%)
 
0.8470 (−15.3%)
 
yotta 1.209 (+20.9%)
 
0.8272 (−17.3%)
 

Consumer confusion

In the early days of computers (roughly, prior to the advent of personal computers) there was little or no consumer confusion because of the technical sophistication of the buyers and their familiarity with the products. In addition, it was common for computer manufacturers to specify their products with capacities in full precision.[40]

In the personal computing era, one source of consumer confusion is the difference in the way many operating systems display hard drive sizes, compared to the way hard drive manufacturers describe them. Hard drives are specified and sold using "GB" and "TB" in their decimal meaning: one billion and one trillion bytes. Many operating systems and other software, however, display hard drive and file sizes using "MB", "GB" or other SI-looking prefixes in their binary sense, just as they do for displays of RAM capacity. For example, many such systems display a hard drive marketed as "160 GB" as "149.05 GB". The earliest known presentation of hard disk drive capacity by an operating system using "KB" or "MB" in a binary sense is 1984;[41] earlier operating systems generally presented the hard disk drive capacity as an exact number of bytes, with no prefix of any sort, for example, in the output of the MS-DOS or PC DOS CHKDSK command.

Legal disputes

The different interpretations of disk size prefixes has led to three significant class action lawsuits against digital storage manufacturers. One case involved flash memory and the other two involved hard disk drives. Two of these were settled with the manufacturers admitting no wrongdoing but agreeing to clarify the storage capacity of their products on the consumer packaging. Flash memory and hard disk manufacturers now have disclaimers on their packaging and web sites clarifying the formatted capacity of the devices or defining MB as 1 million bytes and 1 GB as 1 billion bytes.[42][43][44][45]

Willem Vroegh v. Eastman Kodak Company

On 20 February 2004, Willem Vroegh filed a lawsuit against Lexar Media, Dane–Elec Memory, Fuji Photo Film USA, Eastman Kodak Company, Kingston Technology Company, Inc., Memorex Products, Inc.; PNY Technologies Inc., SanDisk Corporation, Verbatim Corporation, and Viking Interworks alleging that their descriptions of the capacity of their flash memory cards were false and misleading.

Vroegh claimed that a 256 MB Flash Memory Device had only 244 MB of accessible memory. "Plaintiffs allege that Defendants marketed the memory capacity of their products by assuming that one megabyte equals one million bytes and one gigabyte equals one billion bytes." The plaintiffs wanted the defendants to use the traditional values of 10242 for megabyte and 10243 for gigabyte. The plaintiffs acknowledged that the IEC and IEEE standards define a MB as one million bytes but stated that the industry has largely ignored the IEC standards.[46]

The manufacturers agreed to clarify the flash memory card capacity on the packaging and web sites.[47] The consumers could apply for "a discount of ten percent off a future online purchase from Defendants' Online Stores Flash Memory Device".[48]

Orin Safier v. Western Digital Corporation

On 7 July 2005, an action entitled Orin Safier v. Western Digital Corporation, et al. was filed in the Superior Court for the City and County of San Francisco, Case No. CGC-05-442812. The case was subsequently moved to the Northern District of California, Case No. 05-03353 BZ.[49]

Although Western Digital maintained that their usage of units is consistent with "the indisputably correct industry standard for measuring and describing storage capacity", and that they "cannot be expected to reform the software industry", they agreed to settle in March 2006 with 14 June 2006 as the Final Approval hearing date.[50]

Western Digital offered to compensate customers with a free download of backup and recovery software valued at US$30. They also paid $500,000 in fees and expenses to San Francisco lawyers Adam Gutride and Seth Safier, who filed the suit. The settlement called for Western Digital to add a disclaimer to their later packaging and advertising.[51][52][53]

Cho v. Seagate Technology (US) Holdings, Inc.

A lawsuit (Cho v. Seagate Technology (US) Holdings, Inc., San Francisco Superior Court, Case No. CGC-06-453195) was filed against Seagate Technology, alleging that Seagate overrepresented the amount of usable storage by 7% on hard drives sold between March 22, 2001 and September 26, 2007. The case was settled without Seagate admitting wrongdoing, but agreeing to supply those purchasers with free backup software or a 5% refund on the cost of the drives.[54]

Unique binary prefixes

Early suggestions

While early computer scientists typically used k to mean 1000, some recognized the convenience that would result from working with multiples of 1024 and the confusion that resulted from using the same prefixes for two different meanings.

Several proposals for unique binary prefixes[defn. 2] were made in 1968. Donald Morrison proposed to use the Greek letter kappa (κ) to denote 1024, κ2 to denote 1024×1024, and so on.[55] (At the time, memory size was small, and only K was in widespread use.) Wallace Givens responded with a proposal to use bK as an abbreviation for 1024 and bK2 or bK2 for 1024×1024, though he noted that neither the Greek letter nor lowercase letter b would be easy to reproduce on computer printers of the day.[56] Bruce Alan Martin of Brookhaven National Laboratory further proposed that the prefixes be abandoned altogether, and the letter B be used for base-2 exponents, similar to E in decimal scientific notation, to create shorthands like 3B20 for 3×220,[57] a convention still used on some calculators to present binary floating point-numbers today.[58]

None of these gained much acceptance, and capitalization of the letter K became the de facto standard for indicating a factor of 1024 instead of 1000, although this could not be extended to higher powers.

As the discrepancy between the two systems increased in the higher-order powers, more proposals for unique prefixes were made. In 1996, Markus Kuhn proposed a system with di prefixes, like the "dikilobyte" (K₂B or K2B).[59] Donald Knuth, who uses decimal notation like 1 MB = 1000 kB,[60] expressed "astonishment" that the IEC proposal was adopted, calling them "funny-sounding" and opining that proponents were assuming "that standards are automatically adopted just because they are there." Knuth proposed that the powers of 1024 be designated as "large kilobytes" and "large megabytes" (abbreviated KKB and MMB, as "doubling the letter connotes both binary-ness and large-ness").[61] Double prefixes were already abolished from SI, however, having a multiplicative meaning ("MMB" would be equivalent to "TB"), and this proposed usage never gained any traction.

IEC prefixes

The set of binary prefixes that were eventually adopted, now referred to as the "IEC prefixes",[defn. 5] were first proposed by the International Union of Pure and Applied Chemistry's (IUPAC) Interdivisional Committee on Nomenclature and Symbols (IDCNS) in 1995. At that time, it was proposed that the terms kilobyte and megabyte be used only for 103 bytes and 106 bytes, respectively. The new prefixes kibi (kilobinary), mebi (megabinary), gibi (gigabinary) and tebi (terabinary) were also proposed at the time, and the proposed symbols for the prefixes were kb, Mb, Gb and Tb respectively, rather than Ki, Mi, Gi and Ti.[62] The proposal was not accepted at the time.

The Institute of Electrical and Electronic Engineers (IEEE) began to collaborate with the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) to find acceptable names for binary prefixes. IEC proposed kibi, mebi, gibi and tebi, with the symbols Ki, Mi, Gi and Ti respectively, in 1996.[63]

The names for the new prefixes are derived from the original SI prefixes combined with the term binary, but contracted, by taking the first two letters of the SI prefix and "bi" from binary. The first letter of each such prefix is therefore identical to the corresponding SI prefixes, except for "K", which is used interchangeably with "k", whereas in SI, only the lower-case k represents 1000.

The IEEE decided that their standards would use the prefixes kilo, etc. with their metric definitions, but allowed the binary definitions to be used in an interim period as long as such usage was explicitly pointed out on a case-by-case basis.[64]

Adoption by IEC, NIST and ISO

In January 1999, the IEC published the first international standard (IEC 60027-2 Amendment 2) with the new prefixes, extended up to pebi (Pi) and exbi (Ei).[65][66]

The IEC 60027-2 Amendment 2 also states that the IEC position is the same as that of BIPM (the body that regulates the SI system); the SI prefixes retain their definitions in powers of 1000 and are never used to mean a power of 1024.

In usage, products and concepts typically described using powers of 1024 would continue to be, but with the new IEC prefixes. For example, a memory module of 536870912 bytes (512 × 1048576) would be referred to as 512 MiB or 512 mebibytes instead of 512 MB or 512 megabytes. Conversely, since hard drives have historically been marketed using the SI convention that "giga" means 1000000000, a "500 GB" hard drive would still be labeled as such. According to these recommendations, operating systems and other software would also use binary and SI prefixes in the same way, so the purchaser of a "500 GB" hard drive would find the operating system reporting either "500 GB" or "466 GiB", while 536870912 bytes of RAM would be displayed as "512 MiB".

The second edition of the standard, published in 2000,[67] defined them only up to exbi,[68] but in 2005, the third edition added prefixes zebi and yobi, thus matching all SI prefixes with binary counterparts.[69]

The harmonized ISO/IEC IEC 80000-13:2008 standard cancels and replaces subclauses 3.8 and 3.9 of IEC 60027-2:2005 (those defining prefixes for binary multiples). The only significant change is the addition of explicit definitions for some quantities.[70] In 2009, the prefixes kibi-, mebi-, etc. were defined by ISO 80000-1 in their own right, independently of the kibibyte, mebibyte, and so on.

The BIPM standard JCGM 200:2012 "International vocabulary of metrology - Basic and general concepts and associated terms (VIM), 3rd edition" lists the IEC binary prefixes and states "SI prefixes refer strictly to powers of 10, and should not be used for powers of 2. For example, 1 kilobit should not be used to represent 1024 bits (210 bits), which is 1 kibibit." [71]

Specific units of IEC 60027-2 A.2 and ISO/IEC 80000
IEC prefix Representations Customary prefix
Name Symbol Base 2 Base 1024 Value Base 10 Name Symbol
kibi Ki 210 10241 1024 1.02×103 kilo k[13] or K
mebi Mi 220 10242 1048576 1.05×106 mega M
gibi Gi 230 10243 1073741824 1.07×109 giga G
tebi Ti 240 10244 1099511627776 1.10×1012 tera T
pebi Pi 250 10245 1125899906842624 1.13×1015 peta P
exbi Ei 260 10246 1152921504606846976 1.15×1018 exa E
zebi Zi 270 10247 1180591620717411303424 1.18×1021 zetta Z
yobi Yi 280 10248 1208925819614629174706176 1.21×1024 yotta Y

Other standards bodies and organizations

The IEC standard binary prefixes are now supported by other standardization bodies and technical organizations.

The United States National Institute of Standards and Technology (NIST) supports the ISO/IEC standards for "Prefixes for binary multiples" and has a web site documenting them, describing and justifying their use. NIST suggests that in English, the first syllable of the name of the binary-multiple prefix should be pronounced in the same way as the first syllable of the name of the corresponding SI prefix, and that the second syllable should be pronounced as bee.[2] NIST has stated the SI prefixes "refer strictly to powers of 10" and that the binary definitions "should not be used" for them.[72]

The microelectronics industry standards body JEDEC describes the IEC prefixes in its online dictionary.[73] The JEDEC standards for semiconductor memory use the customary prefix symbols K, M, G and T in the binary sense.[74]

On 19 March 2005, the IEEE standard IEEE 1541-2002 ("Prefixes for Binary Multiples") was elevated to a full-use standard by the IEEE Standards Association after a two-year trial period.[75][76] However, as of April 2008, the IEEE Publications division does not require the use of IEC prefixes in its major magazines such as Spectrum[77] or Computer.[78]

The International Bureau of Weights and Measures (BIPM), which maintains the International System of Units (SI), expressly prohibits the use of SI prefixes to denote binary multiples, and recommends the use of the IEC prefixes as an alternative since units of information are not included in SI.[79][80]

The Society of Automotive Engineers (SAE) prohibits the use of SI prefixes with anything but a power-of-1000 meaning, but does not recommend or otherwise cite the IEC binary prefixes.[81]

The European Committee for Electrotechnical Standardization (CENELEC) adopted the IEC-recommended binary prefixes via the harmonization document HD 60027-2:2003-03.[82] The European Union (EU) has required the use of the IEC binary prefixes since 2007.[83]

Current practice

Most computer hardware uses SI prefixes[defn. 1] to state capacity and define other performance parameters such as data rate. Main and cache memories are notable exceptions.

Capacities of main memory and cache memory are usually expressed with customary binary prefixes[defn. 4][84][85][86][87][88] On the other hand, flash memory, like that found in solid state drives, mostly uses SI prefixes[defn. 1] to state capacity.

Some operating systems and other software continue to use the customary binary prefixes in displays of memory, disk storage capacity, and file size, but SI prefixes[defn. 1] in other areas such as network communication speeds and processor speeds.

In the following subsections, unless otherwise noted, examples are first given using the common prefixes used in each case, and then followed by interpretation using other notation where appropriate.

Operating systems

Prior to the release of Macintosh System Software (1984), file sizes were typically reported by the operating system without any prefixes.[citation needed] Today, most operating systems report file sizes with prefixes.

Software

As of February 2010, most software does not distinguish symbols for binary and decimal prefixes.[defn. 3] The IEC binary naming convention has been adopted by a few, but this is not used universally.

One of the stated goals of the introduction of the IEC prefixes was "to preserve the SI prefixes as unambiguous decimal multipliers."[75] Programs such as fdisk/cfdisk, parted, and apt-get use SI prefixes with their decimal meaning.

Example of the use of IEC binary prefixes in the Linux operating system displaying traffic volume on a network interface in kibibytes (KiB) and mebibytes (MiB), as obtained with the ifconfig utility:

eth0      Link encap:Ethernet  HWaddr 00:14:A0:B0:7A:42
          inet6 addr: 2001:491:890a:1:214:a5ff:febe:7a42/64 Scope:Global
          inet6 addr: fe80::214:a5ff:febe:7a42/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:254804 errors:0 dropped:0 overruns:0 frame:0
          TX packets:756 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18613795 (17.7 MiB)  TX bytes:45708 (44.6 KiB)

Software that uses standard SI prefixes for powers of 1000, but not IEC binary prefixes for powers of 1024, includes:

  • Mac OS X v10.6 and later for hard drive and file sizes[95][96]

Software that uses IEC binary prefixes for powers of 1024 and uses standard SI prefixes for powers of 1000 includes:

Computer hardware

Hardware types that use powers-of-1024 multipliers, such as memory, continue to be marketed with customary binary prefixes.

Computer memory

The 536870912 byte (512×220) capacity of these RAM modules is stated as "512 MB" on the label.

Measurements of most types of electronic memory such as RAM and ROM are given using customary binary prefixes (kilo, mega, and giga). This includes some flash memory, like EEPROMs. For example, a "512-megabyte" memory module is 512×220 bytes (512 × 1048576, or 536870912).

JEDEC Solid State Technology Association, the semiconductor engineering standardization body of the Electronic Industries Alliance (EIA), continues to include the customary binary definitions of kilo, mega and giga in their Terms, Definitions, and Letter Symbols document,[111] and uses those definitions in later memory standards[112][113][114][115][116] (See also JEDEC memory standards.)

Many computer programming tasks reference memory in terms of powers of two because of the inherent binary design of current hardware addressing systems. For example, a 16-bit processor register can reference at most 65,536 items (bytes, words, or other objects); this is conveniently expressed as "64K" items. An operating system might map memory as 4096-byte pages, in which case exactly 8192 pages could be allocated within 33554432 bytes of memory: "8K" (8192) pages of "4 kilobytes" (4096 bytes) each within "32 megabytes" (32 MiB) of memory.

Hard disk drives

All hard disk drive manufacturers state capacity using SI prefixes.[defn. 1][117]

Flash drives

USB flash drives, flash-based memory cards like CompactFlash or Secure Digital, and flash-based SSDs use SI prefixes;[defn. 1] for example, a "256 MB" flash card provides at least 256 million bytes (256000000), not 256×1024×1024 (268435456).[45] The flash memory chips inside these devices contain considerably more than the quoted capacities, but much like a traditional hard drive, some space is reserved for internal functions of the flash drive. These include wear leveling, error correction, sparing, and metadata needed by the device's internal firmware.

Floppy drives

Floppy disks have existed in numerous physical and logical formats, and have been sized inconsistently. In part, this is because the end user capacity of a particular disk is a function of the controller hardware, so that the same disk could be formatted to a variety of capacities. In many cases, the media are marketed without any indication of the end user capacity, as for example, DSDD, meaning double-sided double-density.

The last widely adopted diskette was the 3½-inch high density. This has a formatted capacity of 1474560 bytes or 1440 KB (1440 × 1024, using "KB" in the customary binary sense). These are marketed as "HD", or "1.44 MB" or both. This usage creates a third definition of "megabyte" as 1000×1024 bytes.

Most operating systems display the capacity using "MB" in the customary binary sense, resulting in a display of "1.4 MB" (1.40625 MB). Some users have noticed the missing 0.04 MB and both Apple and Microsoft have support bulletins referring to them as 1.4 MB.[37]

The earlier "1200 KB" (1200×1024 bytes) 5¼-inch diskette sold with the IBM PC AT was marketed as "1.2 MB" (1.171875 MiB). The largest 8-inch diskette formats could contain more than a megabyte, and the capacities of those devices were often irregularly specified in megabytes, also without controversy.

Older and smaller diskette formats were usually identified as an accurate number of (binary) KB, for example the Apple Disk II described as "140KB" had a 140×1024-byte capacity, and the original "360KB" double sided, double density disk drive used on the IBM PC had a 360×1024-byte capacity.

In many cases diskette hardware was marketed based on unformatted capacity, and the overhead required to format sectors on the media would reduce the nominal capacity as well (and this overhead typically varied based on the size of the formatted sectors), leading to more irregularities.

Optical discs

The capacities of most optical disc storage media like DVD, Blu-ray Disc, HD DVD and magneto-optical (MO) are given using SI decimal prefixes. A "4.7 GB" DVD has a nominal capacity of about 4.38 GiB.[39] However, CD capacities are always given using customary binary prefixes. Thus a "700-MB" (or "80-minute") CD has a nominal capacity of about 700 MiB (approx 730 MB).[38]

Tape drives and media

Tape drive and media manufacturers use SI decimal prefixes to identify capacity.[118]

Data transmission and clock rates

Certain units are always used with SI decimal prefixes even in computing contexts. Two examples are hertz (Hz), which is used to measure the clock rates of electronic components, and bit/s, used to measure data transmission speed.

  • A 1-GHz processor receives 1000000000 clock ticks per second.
  • A sound file sampled at 44.1 kHz has 44100 samples per second.
  • A 128 kbit/s MP3 stream consumes 128000 bits (16 kilobytes, 15.6 KiB) per second.
  • A 1 Mbit/s Internet connection can transfer 1000000 bits per second (125000 bytes per second ≈ 122 KiB/s, assuming an 8-bit byte and no overhead)
  • A 1 Gbit/s Ethernet connection can transfer 1000000000 bits per second (125000000 bytes per second ≈ 119 MiB/s, assuming an 8-bit byte and no overhead)
  • A 56k modem transfers 56000 bits per second ≈ 6.8 KiB/s.

Bus clock speeds and therefore bandwidths are both quoted using SI decimal prefixes.

  • PC3200 memory on a double data rate bus, transferring 8 bytes per cycle with a clock speed of 200 MHz (200000000 cycles per second) has a bandwidth of 200000000 × 8 × 2 = 3200000000 bytes/second = 3.2 GB/s (about 3.0 GiB/s).
  • A PCI-X bus at 66 MHz (66000000 cycles per second), 64 bits per transfer, has a bandwidth of 66000000 transfers/second × 64 bits/transfer = 4224000000 bits/second, or 528000000 bytes/second, usually quoted as 528 MB/s (about 503 MiB/s).

Use by industry

IEC prefixes are used by Toshiba,[119] IBM, HP to advertise or describe some of their products. According to one HP brochure, [4] "[t]o reduce confusion, vendors are pursuing one of two remedies: they are changing SI prefixes to the new binary prefixes, or they are recalculating the numbers as powers of ten." The IBM Data Center also uses IEC prefixes to reduce confusion.[120] The IBM Style Guide reads[121]

"To help avoid inaccuracy (especially with the larger prefixes) and potential ambiguity, the International Electrotechnical Commission (IEC) in 2000 adopted a set of prefixes specifically for binary multipliers (See IEC 60027-2). Their use is now supported by the United States National Institute of Standards and Technology (NIST) and incorporated into ISO 80000. They are also required by EU law and in certain contexts in the US. However, most documentation and products in the industry continue to use SI prefixes when referring to binary multipliers. In product documentation, follow the same standard that is used in the product itself (for example, in the interface or firmware). Whether you choose to use IEC prefixes for powers of 2 and SI prefixes for powers of 10, or use SI prefixes for a dual purpose ... be consistent in your usage and explain to the user your adopted system."

Websites and government agencies

See also

Definitions

  1. 1.0 1.1 1.2 1.3 1.4 1.5 The term SI prefix or similar refers to prefixes such as kilo, mega, giga, etc., defined by the SI system of units and always used to denote a power of 1000; in other words, always as decimal prefixes.
  2. 2.0 2.1 A binary prefix is a prefix that denotes a power of 1024. For example, in the computer industry's customary practice, one "megabyte" of RAM is 10242 bytes of RAM, one "gigabyte" of RAM is 10243 bytes of RAM, and so on. In the IEC system, these would be expressed as one "mebibyte" and one "gibibyte," respectively. Both are "binary prefixes" in these usages.
  3. 3.0 3.1 A decimal prefix is a prefix that denotes a power of 1000. For example, "kilo" denotes 1000, "mega" denotes 10002 or one million, "giga" denotes 10003 or one billion, and so on. SI prefixes are decimal prefixes.
  4. 4.0 4.1 As used in this article, the term customary binary prefix or similar refers to prefixes such as kilo, mega, giga, etc., borrowed from the similarly named SI prefixes but commonly used to denote a power of 1024.
  5. The term IEC binary prefix or IEC prefix refers to the prefixes such as kibi, mebi, gibi, etc., or their corresponding symbols Ki, Mi, Gi, etc., first adopted by the International Electrotechnical Commission (IEC). Such prefixes are only used with the units bits or bytes (or compound units derived from them such as bytes/second) and always denote powers of 1024; that is, they are always used as binary prefixes. Thus 1 mebibyte of RAM is 10242 bytes of RAM, one gibibyte or 1 GiB of RAM is 10243 bytes, and so on.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found. This lengthy report describes many of the early computers.
  4. Hunting Trouble on 28 Megacycles, A. L. Blais, QST, January 1930.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found. Note: the IBM 704 core memory units had 4096 36-bit words. Up to 32768 words could be installed
  7. Lua error in package.lua at line 80: module 'strict' not found. "The 8K core stores were getting fairly common in this country in 1954. The 32K store started mass production in 1956; it is the standard now for large machines and at least 200 machines of the size (or its equivalent in the character addressable machines) are in existence today (and at least 100 were in existence in mid-1959)." Note: The IBM 1401 was a character addressable computer.
  8. Lua error in package.lua at line 80: module 'strict' not found. Figure 1 gives storage (memory) capacity ranges of the various models in "Capacity 8-bit bytes, 1 K = 1024"
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. IBM invented the disk drive in 1956 and until the late 1960s its drives and their clones were dominant. See, e.g. US vs. IBM antitrust litigation (Jan 1969), especially IBM analyses of Memorex and other disk drive companies.
  21. The CDC Product Line Card unambiguously uses MB to characterize HDD capacity in millions of bytes
  22. 1977 Disk/Trend Report – Rigid Disk Drives, published June 1977
  23. ST506/412 OEM Manual, Seagate Corp. April 1982, para. 1.2
  24. IBM Tells MiniScribe It Is Cutting Back On Winchester Orders, Computer System News, Jan 1, 1984, p. 1
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Seagate Savvio 10K.5 SAS Product Manual, 100628561, Rev D, March 2011, sec 5.2.3, p. 10 (18th page of the pdf), states the drive's sustained transfer speed as "89 to 160 MiB/s" on one line, and "93 to 168 MB/s" on the next line.
  27. Seagate marketing bulletin, Advanced Format 4K Sector Transition Archived October 11, 2014 at the Wayback Machine
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  30. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.[dead link] "kB See kilobyte." "Kbyte Kilobyte. Indicates 210 bytes." "Kilobyte Either 1000 or 210 or 1024 bytes." The standard also defines megabyte and gigabyte with a note that an alternative notation for base 2 is under development.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found. "The 1.44-megabyte (MB) value associated with the 3.5-inch disk format does not represent the actual size or free space of these disks. Although its size has been popularly called 1.44 MB, the correct size is actually 1.40 MB."
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Understanding Recordable and Rewritable DVD Archived January 2, 2011 at the Wayback Machine
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Apple Macintosh which began using "KB" in a binary sense to report HDD capacity beginning 1984.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. http://web.archive.org/web/20120413100902/http://www.sandisk.com/Assets/Categories/Products/sd_capacitydisclaimer.pdf
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. The Art of Computer Programming Volume 1, Donald Knuth, pp. 24 and 94
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Bruce Barrow, "A Lesson in Megabytes", IEEE Standards Bearer, January 1997, page 5
  65. "These prefixes for binary multiples, which were developed by IEC Technical Committee (TC) 25, Quantities and units, and their letter symbols, with the strong support of the International Committee for Weights and Measures (CIPM) and the IEEE, were adopted by the IEC as Amendment 2 to IEC International Standard IEC 60027-2: Letter symbols to be used in electrical technology – Part 2: Telecommunications and electronics."
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. IEC 60027-2 (2000-11) Ed. 2.0
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. International vocabulary of metrology - Basic and general concepts and associated terms (VIM), 3rd edition
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found. Free registration required to download the standard.
  75. 75.0 75.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  76. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  77. Lua error in package.lua at line 80: module 'strict' not found. "A lot can happen in a decade. You can hold the Nokia N800 in your hand, yet it's a near-exact match for a high-end desktop PC from 10 years ago. It has a 320-megahertz processor, 128 megabytes of RAM, and a few gigabytes of available mass storage."
  78. Lua error in package.lua at line 80: module 'strict' not found. "The processor has a memory subsystem with separate first-level 32-Kbyte instruction and data caches, and a 512-Kbyte unified second-level cache." Authors are with IBM.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Rules for SAE Use of SI (Metric) Units – Section C.1.12 – SI prefixes]
  82. [1] Information about the harmonization document (obtainable on order, status: withdrawn)
  83. [2] Information about the EN standardization process.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Dell, Sony Archived August 25, 2015 at the Wayback Machine
  86. Apple Inc., Toshiba
  87. Gateway
    Sun Microsystems Archived February 16, 2012 at the Wayback Machine
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. FreeDOS-32 – Standards Compliance Archived January 12, 2009 at the Wayback Machine
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. archive.netbsd.se Archived October 3, 2011 at the Wayback Machine
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found. (Requires free registration and login.)
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. i.e. see HGST, Samsung, Seagate, Toshiba and Western Digital websites Archived July 18, 2012 at the Wayback Machine[dead link]
  118. see e.g., 3592 Tape Cartridge, ECMA-319, Ultrium-1 etc.
  119. [3]
  120. Data storage values
  121. DeRespinis, F., Hayward, P., Jenkins, J., Laird, A., McDonald, L., & Radzinski, E. (2011). The IBM style guide: conventions for writers and editors. IBM Press.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found. – An introduction to binary prefixes
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.—a 1996–1999 paper on bits, bytes, prefixes and symbols
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.—Another description of binary prefixes
  • Lua error in package.lua at line 80: module 'strict' not found.—White-paper on the controversy over drive capacities

External links