Английская Википедия:Binary prefix

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:About Шаблон:Use dmy dates

Шаблон:Bit and byte prefixes

A binary prefix is a unit prefix that indicates a multiple of a unit of measurement by an integer power of two. The most commonly used binary prefixes are kibi (symbol Ki, meaning 210 = 1024), mebi (Mi, 220 = Шаблон:Val), and gibi (Gi, 230 = Шаблон:Val). They are most often used in information technology as multipliers of bit and byte, when expressing the capacity of storage devices or the size of computer files.

The binary prefixes "kibi", "mebi", etc. were defined in 1999 by the International Electrotechnical Commission (IEC), in the IEC 60027-2 standard (Amendment 2). They were meant to replace the metric (SI) decimal power prefixes, such as "kilo" ("k", 103 = 1000), "mega" ("M", 106 = Шаблон:Val) and "giga" ("G", 109 = Шаблон:Val),[1] that were commonly used in the computer industry to indicate the nearest powers of two. For example, a memory module whose capacity was specified by the manufacturer as "2 megabytes" or "2 MB" would hold 2 × 220 = Шаблон:Val bytes, instead of 2 × 106 = Шаблон:Val.

On the other hand, a hard disk whose capacity is specified by the manufacturer as "10 gigabytes" or "10 GB", holds 10 × 109 = Шаблон:Val bytes, or a little more than that, but less than 10 × 230 = Шаблон:Val and a file whose size is listed as "2.3 GB" may have a size closer to 2.3 × 230 ≈ Шаблон:Val or to 2.3 × 109 = Шаблон:Val, depending on the program or operating system providing that measurement. This kind of ambiguity is often confusing to computer system users and has resulted in lawsuits.[2][3] The IEC 60027-2 binary prefixes have been incorporated in the ISO/IEC 80000 standard and are supported by other standards bodies, including the BIPM, which defines the SI system,[1]Шаблон:Rp the US NIST,[4][5] and the European Union.

Prior to the 1999 IEC standard, some industry organizations, such as the Joint Electron Device Engineering Council (JEDEC), attempted to redefine the terms kilobyte, megabyte, and gigabyte, and the corresponding symbols KB, MB, and GB in the binary sense, for use in storage capacity measurements. However, other computer industry sectors (such as magnetic storage) continued using those same terms and symbols with the decimal meaning. Since then, the major standards organizations have expressly disapproved the use of SI prefixes to denote binary multiples, and recommended or mandated the use of the IEC prefixes for that purpose, but the use of SI prefixes has persisted in some fields.

While the binary prefixes are almost always used with the units of information, bits and bytes, they may be used with any other unit of measure, when convenient. For example, in signal processing one may need binary multiples of the frequency unit hertz (Hz), for example the kibihertz (KiHz), equal to Шаблон:Nowrap.[6][7]

Definitions

Шаблон:Anchor

Specific units of IEC 60027-2 A.2 and ISO/IEC 80000:13-2008
IEC prefix Representations
Name Symbol Base 2 Base 1024 Value Base 10
kibi Ki 210 10241 Шаблон:Val = Шаблон:Val
mebi Mi 220 10242 Шаблон:Val ≈ Шаблон:Val
gibi Gi 230 10243 Шаблон:Val ≈ Шаблон:Val
tebi Ti 240 10244 Шаблон:Val ≈ Шаблон:Val
pebi Pi 250 10245 Шаблон:Val ≈ Шаблон:Val
exbi Ei 260 10246 Шаблон:Val ≈ Шаблон:Val
zebi Zi 270 10247 Шаблон:Val ≈ Шаблон:Val
yobi Yi 280 10248 Шаблон:Val ≈ Шаблон:Val

Шаблон:AnchorIn 2022, the International Bureau of Weights and Measures (BIPM) adopted the decimal prefixes ronna for 10009 and quetta for 100010.[8][9] In analogy to the existing binary prefixes, a consultation paper of the International Committee for Weights and Measures' Consultative Committee for Units (CCU) suggested the prefixes robi (Ri, 10249) and quebi (Qi, 102410) for their binary counterparts,[10] but Шаблон:As of, no corresponding binary prefixes have been adopted.[11]

Comparison of binary and decimal prefixes

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 27% for the quetta prefix. Although the prefixes ronna and quetta have been defined, as of 2022 no names have been officially assigned to the corresponding binary prefixes.

Файл:Binaryvdecimal.svg
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 kibi 1.024   (+2.4%)
 
 0.9766   (−2.3%)
 
mega mebi 1.049   (+4.9%)
 
 0.9537   (−4.6%)
 
giga gibi 1.074   (+7.4%)
 
 0.9313   (−6.9%)
 
tera tebi 1.100 (+10.0%)
 
 0.9095   (−9.1%)
 
peta pebi 1.126 (+12.6%)
 
 0.8882 (−11.2%)
 
exa exbi 1.153 (+15.3%)
 
 0.8674 (−13.3%)
 
zetta zebi 1.181 (+18.1%)
 
 0.8470 (−15.3%)
 
yotta yobi 1.209 (+20.9%)
 
 0.8272 (−17.3%)
 
ronna  — 1.238 (+23.8%)
 
 0.8078 (−19.2%)
 
quetta  — 1.268 (+26.8%)
 
 0.7889 (−21.1%)
 

History

Шаблон:See also

Early prefixes

The original metric system adopted by France in 1795 included two binary prefixes named double- (2×) and demi- (Шаблон:Sfrac×).[12] However, these were not retained when the SI prefixes were internationally adopted by the 11th CGPM conference in 1960.

Storage capacity

Main memory

Early computers used one of two addressing methods to access the system memory; binary (base 2) or decimal (base 10).[13] For example, the IBM 701 (1952) used a binary methods and could address 2048 words of 36 bits each, while the IBM 702 (1953) used a decimal system, 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 states of their address lines map to a valid address, allowing easy aggregation into a larger block of memory with contiguous addresses.

While early documentation specified those memory sizes as exact numbers such as 4096, 8192, or Шаблон:Val units (usually words, bytes, or bits), computer professionals also started using the long-established metric system prefixes "kilo", "mega", "giga", etc., defined to be powers of 10,[1] to mean instead the nearest powers of two; namely, 210 = 1024, 220 = 10242, 230 = 10243, etc.[14][15] The corresponding metric prefix symbols ("k", "M", "G", etc.) where used with the same binary meanings.[16][17] The symbol for 210 = 1024 could be written either in lower case ("k")[18][19][20] or in uppercase ("K"). The latter was often used intentionally to indicate the binary rather than decimal meaning.[21] This convention, which could not be extended to higher powers, was widely used in the documentation of the IBM 360 (1964)[21] and of the IBM System/370 (1972),[22] of the CDC 7600,[23] of the DEC PDP-11/70 (1975)[24] and of the DEC VAX-11/780 (1977).Шаблон:Cn

In other documents, however, the metric prefixes and their symbols were used to denote powers of 10, but usually with the understanding that the values given were approximate, often truncated down. Thus, for example, a 1967 document by Control Data Corporation (CDC) abbreviated "216 = 64 × 1024 = Шаблон:Val words" as "65K words" (rather than "64K" or "66K"),[25], while the documentation of the HP 21MX real-time computer (1974) denoted 3 × 216 = 192 × 1024 = Шаблон:Val as "196K" and 220 = Шаблон:Val as "1M".[26]

These three possible meanings of "k" and "K" ("1024", "1000", or "approximately 1000") were used loosely around the same time, sometimes by the same company. The HP 3000 business computer (1973) could have "64K", "96K", or "128K" bytes of memory.[27] The use of SI prefixes, and the use of "K" instead of "k" remained popular in computer-related publications well into the 21st century, although the ambiguity persisted. The correct meaning was often clear from the context; for instance, in a binary-addressed computer, the true memory size had to be either a power of 2, or a small integer multiple thereof. Thus a "512 megabyte" RAM module was generally understood to have Шаблон:Nowrap = Шаблон:Val bytes, rather than Шаблон:Val.

Hard disks

In specifying disk drive capacities, manufacturers have always used conventional decimal SI prefixes representing powers of 10. Storage in a rotating disk drive is organized in platters and tracks whose sizes and counts are determined by mechanical engineering constraints so that the capacity of a disk drive has hardly ever been a simple multiple of a power of 2. For example, the first commercially sold disk drive, the IBM 350 (1956), had 50 physical disk platters containing a total of Шаблон:Val sectors of 100 characters each, for a total quoted capacity of 5 million characters.[28]

Moreover, since the 1960s, many disk drives used IBM's disk format, where each track was divided into blocks of user-specified size; and the block sizes were recorded on the disk, subtracting from the usable capacity. For example, the|IBM 3336]] disk pack was quoted to have a 200-megabyte capacity, achieved only with a single Шаблон:Val-byte block in each of its 808 x 19 tracks.

Decimal megabytes were used for disk capacity by the CDC in 1974.[29] The Seagate ST-412,[30] one of several types installed in the IBM PC/XT,[31] had a capacity of Шаблон:Val when formatted as 306 × 4 tracks and 32 256-byte sectors per track, which was quoted as "Шаблон:Nowrap".[32] Similarly, a "Шаблон:Nowrap" hard drive can be expected to offer only slightly more than Шаблон:Val = Шаблон:Val, bytes, not Шаблон:Nowrap (which would be about Шаблон:Val bytes or "Шаблон:Nowrap"). The first terabyte (SI prefix, Шаблон:Val bytes) hard disk drive was introduced in 2007.[33] Decimal prefixes were generally used by information processing publications when comparing hard disk capacities.[34]

Users must be aware that some programs and operating systems, such as Microsoft Windows and Classic Mac OS, may use "MB" and "GB" to denote binary prefixes even when displaying disk drive capacities. Thus, for example, the capacity of a "10 MB" (decimal "M") disk drive could be reported as "9.56 MB", and that of a "300 GB" drive as "279.4 GB". Good software and documentation should specify clearly whether "K", "M", "G" mean binary or decimal multipliers.[35][36] Some operating systems, such as Mac OS X,[37] Ubuntu,[38] and Debian,[39] may use "MB" and "GB" to denote decimal prefixes when displaying disk drive capacities.

Floppy disks

Floppy disks used a variety of formats, and their capacities was usually specified with SI-like prefixes "K" and "M" with either decimal or binary meaning. The capacity of the disks was often specified without accounting for the internal formatting overhead, leading to more irregularities.

The early 8-inch diskette formats could contain less than a megabyte with the capacities of those devices specified in kilobytes, kilobits or megabits.[40][41]

The 5.25-inch diskette sold with the IBM PC AT could hold Шаблон:Nowrap = Шаблон:Val bytes, and thus was marketed as "Шаблон:Nowrap" with the binary sense of "KB".Шаблон:Cn However, the capacity was also quoted "Шаблон:Nowrap",Шаблон:Cn which was a hybrid decimal and binary notation, since the "M" meant 1000 × 1024. The precise value was Шаблон:Val (decimal) or Шаблон:Val (binary).

The 5.25-inch Apple Disk II had 256 bytes per sector, 13 sectors per track, 35 tracks per side, or a total capacity of Шаблон:Val bytes. It was later upgraded to 16 sectors per track, giving a total of Шаблон:Nowrap = Шаблон:Val bytes, which was described as "140KB" using the binary sense of "K".

The most recent version of the physical hardware, the "3.5-inch diskette" cartridge, had 720 512-byte blocks (single-sided). Since two blocks comprised 1024 bytes, the capacity was quoted "360 KB", with the binary sense of "K". On the other hand, the quoted capacity of "1.44 MB" of the High Density ("HD") version was again a hybrid decimal and binary notation, since it meant 1440 pairs of 512-byte sectors, or Шаблон:Nowrap = Шаблон:Val. Some operating systems displayed the capacity of those disks using the binary sense of "MB", as "1.4 MB" (which would be Шаблон:Nowrap ≈ Шаблон:Val). User complaints forced both AppleШаблон:Cn and Microsoft[42] to issue support bulletins explaining the discrepancy.

Optical disks

When specifying the capacities of optical compact discs, "megabyte" and "MB" usually mean 10242 bytes. Thus a "700-MB" (or "80-minute") CD has a nominal capacity of about Шаблон:Val, which is approximately Шаблон:Val (decimal).[43]

On the other hand, capacities of other optical disc storage media like DVD, Blu-ray Disc, HD DVD and magneto-optical (MO) have been generally specified in decimal gigabytes ("GB"), that is, 10003 bytes. In particular, a typical "Шаблон:Nowrap" DVD has a nominal capacity of about Шаблон:Nowrap, which is about Шаблон:Nowrap.[44]

Tape drives and media

Tape drive and media manufacturers have generally used SI decimal prefixes to specify the maximum capacity,[45][46] although the actual capacity would depend on the block size used when recording.

Data and clock rates

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 Шаблон:Nowrap, that is Шаблон:Val.

Similarly, digital information transfer rates are quoted using decimal prefixe. The Parallel ATA "100 MB/s" disk interface can transfer Шаблон:Val bytes per second, and a "56 Kb/s" modem transmits Шаблон:Val bits per second. Seagate specified the sustained transfer rate of some hard disk drive models with both decimal and IEC binary prefixes.[35] The standard sampling rate of music compact disks, quoted as Шаблон:Val, is indeed Шаблон:Val samples per second.Шаблон:Cn A Шаблон:Nowrap Ethernet interface can receive or transmit up to 109 bits per second, or Шаблон:Val bytes per second within each packet. A "56k" modem can encode or decode up to Шаблон:Val bits per second.

Decimal SI prefixes are also generally used for processor-memory data transfer speeds. A PCI-X bus with Шаблон:Val clock and 64 bits wide can transfer Шаблон:Val 64-bit words per second, or Шаблон:Val = Шаблон:Val, which is usually quoted as Шаблон:Val. A PC3200 memory on a double data rate bus, transferring 8 bytes per cycle with a clock speed of Шаблон:Val has a bandwidth of Шаблон:Nowrap = Шаблон:Val, which would be quoted as Шаблон:Val.

Ambiguous standards

The ambiguous usage of the prefixes "kilo ("K" or "k"), "mega" ("M"), and "giga" ("G"), as meaning both powers of 1000 or (in computer contexts) of 1024, has been recorded in popular dictionaries,[47][48][49] and even in some obsolete standards, such as ANSI/IEEE 1084-1986[50] and ANSI/IEEE 1212-1991,[51] IEEE 610.10-1994,[52] and IEEE 100-2000.[53] Some of these standards specifically limited the binary meaning to multiples of "byte" ("B") or "bit" ("b").

Early binary prefix proposals

Before the IEC standard, several alternative proposals existed for unique binary prefixes, starting in the late 1960s. In 1996, Markus Kuhn proposed the extra prefix "di" and the symbol suffix or subscript "2" to mean "binary"; so that, for example, "one dikilobyte" would mean "1024 bytes", denoted "K2B" or "K2B".[54]

In 1968, Donald Morrison proposed to use the Greek letter kappa (κ) to denote 1024, κ2 to denote 10242, and so on.[55] (At the time, memory size was small, and only K was in widespread use.) In the same year, Wallace Givens responded with a suggestion to use bK as an abbreviation for 1024 and bK2 or bK2 for 10242, 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 proposed that, instead of prefixes, binary powers of two were indicated by the letter B followed by the exponent, similar to E in decimal scientific notation. Thus one would write 3B20 for Шаблон:Nowrap.[57] This convention is still used on some calculators to present binary floating point-numbers today.[58]

In 1969, Donald Knuth, who uses decimal notation like 1 MB = 1000 kB,[59] proposed that the powers of 1024 be designated as "large kilobytes" and "large megabytes", with abbreviations KKB and MMB.[60] However, the use of double SI prefixes, although rejected by the BIPM, had already been given a multiplicative meaning;Шаблон:Cn so that "Шаблон:Nowrap" could be understood as "(106)2 bytes, that is, "Шаблон:Nowrap".

Consumer confusion

The ambiguous meanings of "kilo", "mega", "giga", etc., has caused significant consumer confusion, especially in the personal computer era. A common source of confusion was the discrepancy between the capacities of hard drives specified by manufacturers, using those prefixes in the decimal sense, and the numbers reported by operating systems and other software, that used them in the binary sense, such as the Apple in 1984.[61] For example, a hard drive marketed as "Шаблон:Nowrap" could be reported as having only "Шаблон:Nowrap". The confusion was compounded by fact that RAM manufacturers used the binary sense too.

Legal disputes

The different interpretations of disk size prefixes led to class action lawsuits against digital storage manufacturers. These cases involved both flash memory and hard disk drives.

Early cases

Early cases (2004–2007) were settled prior to any court ruling with the manufacturers admitting no wrongdoing but agreeing to clarify the storage capacity of their products on the consumer packaging. Accordingly, many flash memory and hard disk manufacturers have disclosures 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.[62][63][64][65]

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 customary 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.[66]

The parties agreed that manufacturers could continue to use the decimal definition so long as the definition was added to the packaging and web sites.[67] The consumers could apply for "a discount of ten percent off a future online purchase from Defendants' Online Stores Flash Memory Device".[68]

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.[69]

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.[70]

Western Digital offered to compensate customers with a free download of backup and recovery software valued at US$30. They also paid $Шаблон:Val 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.[71][72][73] Western Digital had this footnote in their settlement. "Apparently, Plaintiff believes that he could sue an egg company for fraud for labeling a carton of 12 eggs a 'dozen', because some bakers would view a 'dozen' as including 13 items."[74]

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 22 March 2001 and 26 September 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.[75]

Dinan et al. v. SanDisk LLC

On 22 January 2020, the district court of the Northern District of California ruled in favor of the defendant, SanDisk, upholding its use of "GB" to mean Шаблон:Val.[76]

IEC 1999 Standard

In 1995, the International Union of Pure and Applied Chemistry's (IUPAC) Interdivisional Committee on Nomenclature and Symbols (IDCNS) proposed the prefixes "kibi" (short for "kilobinary"), "mebi" ("megabinary"), "gibi" ("gigabinary") and "tebi" ("terabinary"), with respective symbols "kb", "Mb", "Gb" and "Tb",[77] for binary multipliers. The proposal suggested that the SI prefixes should be used only for powers of 10; so that a disk drive capacity of "500 gigabytes", "0.5 terabytes", "500 GB", or "0.5 TB" should all mean Шаблон:Nowrap bytes, exactly or approximately, rather than Шаблон:Nowrap (= Шаблон:Val) or Шаблон:Nowrap (= Шаблон:Val).

The proposal was not accepted by IUPAC at the time, but was taken up in 1996 by the Institute of Electrical and Electronics Engineers (IEEE) in collaboration with the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC). The prefixes "kibi", "mebi", "gibi" and "tebi" were retained, but with the symbols "Ki" (with capital "K"), "Mi", "Gi" and "Ti" respectively.[78]

In January 1999, the IEC published this proposal, with additional prefixes "pebi" ("Pi") and "exbi" ("Ei"), as an international standard (IEC 60027-2 Amendment 2)[79][80][81] The standard reaffirmed the BIPM's position that the SI prefixes should always denote powers of 10. The third edition of the standard, published in 2005, added prefixes "zebi" and "yobi", thus matching all then-defined SI prefixes with binary counterparts.[82]

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.[83] 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 Шаблон:Val bits (210 bits), which is 1 kibibit."[84]

The IEC 60027-2 standard recommended operating systems and other software were updated to use binary or decimal prefixes consistently, but incorrect usage of SI prefixes for binary multiples is still common. At the time, 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.[85]

Other standards bodies and organizations

The IEC standard binary prefixes are 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 page[86] 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.[5] NIST has stated the SI prefixes "refer strictly to powers of 10" and that the binary definitions "should not be used" for them.[87]

As of 2014, the microelectronics industry standards body JEDEC describes the IEC prefixes in its online dictionary, but acknowledges that the SI prefixes and the symbols "K", "M" and "G" are still commonly used with the binary sense for memory sizes.[88][89]

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.[90][91] Шаблон:As of, the IEEE Publications division does not require the use of IEC prefixes in its major magazines such as Spectrum[92] or Computer.[93]

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 the SI.[94][1]

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

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

Current practice

Файл:Elixir M2U51264DS8HC3G-5T 20060320.jpg
The Шаблон:Val-byte capacity of these RAM modules is stated as "512 MB" on the label.

Some computer industry participants, such as Hewlett-Packard (HP),[98] and IBM[99][100] have adopted or recommended IEC binary prefixes as part of their general documentation policies.

As of 2023, the use of SI prefixes with the binary meanings is still prevalent for specifying the capacity of the main memory of computers, of RAM, ROM, EPROM, and EEPROM chips and modules, and of the cache of computer processors. For example, a "512-megabyte" or "512 MB" memory module holds 512 MiB; that is, 512 × 220 bytes, not 512 × 106 bytes.[101][102][103][104]

JEDEC continues to include the customary binary definitions of "kilo", "mega", and "giga" in the document Terms, Definitions, and Letter Symbols,[105] and, Шаблон:Asof, still used those definitions in their memory standards.[106][107][108][109][110]

On the other hand, the SI prefixes with powers of ten meanings are generally used for the capacity of external storage units, such as disk drives,[111][112][113][114][115] solid state drives, and USB flash drives,[65] except for some flash memory chips intended to be used as EEPROMs. However, some disk manufacturers have used the IEC prefixes to avoid confusion.[116] The decimal meaning of SI prefixes is usually also intended in measurements of data transfer rates, and clock speeds.Шаблон:Cn

Some operating systems and other software use either the IEC binary multiplier symbols ("Ki", "Mi", etc.)[117][118][119][120][121][122] or the SI multiplier symbols ("k", "M", "G", etc.) with decimal meaning. Some programs, such as the Linux/GNU ls command, let the user choose between binary or decimal multipliers. However, some continue to use the SI symbols with the binary meanings, even when reporting disk or file sizes. Some programs may also use "K" instead of "k", with either meaning.Шаблон:Citation needed

Файл:GParted 0.3.5 -- 2008, 06.png
Linux GNOME's partition editor uses IEC prefixes to display partition sizes. The total capacity of the 120 × 109-byte disk is displayed as "111.79 GiB".
Файл:GNOME System Monitor memory size and network rate.png
GNOME's system monitor uses IEC prefixes to show memory size and networking data rate.

See also

References

Шаблон:Reflist

Further reading

External links

Шаблон:Computer Storage Volumes

Партнерские ресурсы
Криптовалюты
Магазины
Хостинг
Разное

  1. ↑ 1,0 1,1 1,2 1,3 Ошибка цитирования Неверный тег <ref>; для сносок BIPM8 не указан текст
  2. ↑ Ошибка цитирования Неверный тег <ref>; для сносок suitxxxx не указан текст
  3. ↑ Ошибка цитирования Неверный тег <ref>; для сносок sand2021 не указан текст
  4. ↑ Ошибка цитирования Неверный тег <ref>; для сносок NIST1 не указан текст
  5. ↑ 5,0 5,1 Ошибка цитирования Неверный тег <ref>; для сносок NIST2 не указан текст
  6. ↑ Ошибка цитирования Неверный тег <ref>; для сносок pate2011 не указан текст
  7. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ains2022 не указан текст
  8. ↑ Ошибка цитирования Неверный тег <ref>; для сносок BIPM2022 не указан текст
  9. ↑ Ошибка цитирования Неверный тег <ref>; для сносок gibn2022 не указан текст
  10. ↑ Ошибка цитирования Неверный тег <ref>; для сносок brown2023 не указан текст
  11. ↑ Ошибка цитирования Неверный тег <ref>; для сносок brown2022 не указан текст
  12. ↑ Ошибка цитирования Неверный тег <ref>; для сносок frev1795 не указан текст
  13. ↑ Ошибка цитирования Неверный тег <ref>; для сносок weik1961 не указан текст
  14. ↑ Ошибка цитирования Неверный тег <ref>; для сносок blais1930 не указан текст
  15. ↑ Ошибка цитирования Неверный тег <ref>; для сносок liny1972 не указан текст
  16. ↑ Ошибка цитирования Неверный тег <ref>; для сносок real1959 не указан текст
  17. ↑ Ошибка цитирования Неверный тег <ref>; для сносок gruen1960 не указан текст
  18. ↑ Ошибка цитирования Неверный тег <ref>; для сносок horak2008 не указан текст
  19. ↑ Ошибка цитирования Неверный тег <ref>; для сносок dodd1997 не указан текст
  20. ↑ Ошибка цитирования Неверный тег <ref>; для сносок laver1989 не указан текст
  21. ↑ 21,0 21,1 Ошибка цитирования Неверный тег <ref>; для сносок amda1964 не указан текст
  22. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IBM1972 не указан текст
  23. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CDC7600 не указан текст
  24. ↑ Ошибка цитирования Неверный тег <ref>; для сносок bell1975 не указан текст
  25. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CDC1967 не указан текст
  26. ↑ Ошибка цитирования Неверный тег <ref>; для сносок frank1974 не указан текст
  27. ↑ Ошибка цитирования Неверный тег <ref>; для сносок HP1973 не указан текст
  28. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IBM1956 не указан текст
  29. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CDC1974 не указан текст
  30. ↑ Ошибка цитирования Неверный тег <ref>; для сносок seag1982 не указан текст
  31. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CSN1984 не указан текст
  32. ↑ Ошибка цитирования Неверный тег <ref>; для сносок mall2011 не указан текст
  33. ↑ Ошибка цитирования Неверный тег <ref>; для сносок hita2007 не указан текст
  34. ↑ Ошибка цитирования Неверный тег <ref>; для сносок RDD1977 не указан текст
  35. ↑ 35,0 35,1 Ошибка цитирования Неверный тег <ref>; для сносок seaga2011 не указан текст
  36. ↑ Ошибка цитирования Неверный тег <ref>; для сносок seag2010 не указан текст
  37. ↑ Шаблон:Cite web
  38. ↑ Шаблон:Cite web
  39. ↑ Шаблон:Cite web
  40. ↑ Шаблон:Cite web
  41. ↑ Шаблон:Cite magazine
  42. ↑ Ошибка цитирования Неверный тег <ref>; для сносок msoftxxxx не указан текст
  43. ↑ Ошибка цитирования Неверный тег <ref>; для сносок cdromcap не указан текст
  44. ↑ Ошибка цитирования Неверный тег <ref>; для сносок dvdcap не указан текст
  45. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IBMt2016 не указан текст
  46. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ECMA2013 не указан текст
  47. ↑ Ошибка цитирования Неверный тег <ref>; для сносок webster не указан текст
  48. ↑ Ошибка цитирования Неверный тег <ref>; для сносок metadict не указан текст
  49. ↑ Ошибка цитирования Неверный тег <ref>; для сносок oxford не указан текст
  50. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ansi1986 не указан текст
  51. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ieee1992 не указан текст
  52. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ieee1994 не указан текст
  53. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ieee2000 не указан текст
  54. ↑ Ошибка цитирования Неверный тег <ref>; для сносок kuhn1996 не указан текст
  55. ↑ Ошибка цитирования Неверный тег <ref>; для сносок morr1968 не указан текст
  56. ↑ Ошибка цитирования Неверный тег <ref>; для сносок give1968 не указан текст
  57. ↑ Ошибка цитирования Неверный тег <ref>; для сносок mart1968 не указан текст
  58. ↑ Ошибка цитирования Неверный тег <ref>; для сносок schw1993 не указан текст
  59. ↑ Ошибка цитирования Неверный тег <ref>; для сносок knuth2016 не указан текст
  60. ↑ Ошибка цитирования Неверный тег <ref>; для сносок knuth1999 не указан текст
  61. ↑ Ошибка цитирования Неверный тег <ref>; для сносок apple1984 не указан текст
  62. ↑ Ошибка цитирования Неверный тег <ref>; для сносок wdc2007 не указан текст
  63. ↑ Ошибка цитирования Неверный тег <ref>; для сносок flash2016 не указан текст
  64. ↑ Ошибка цитирования Неверный тег <ref>; для сносок sand2013 не указан текст
  65. ↑ 65,0 65,1 Ошибка цитирования Неверный тег <ref>; для сносок sd-cap-disclaimer не указан текст
  66. ↑ Ошибка цитирования Неверный тег <ref>; для сносок vreo2005 не указан текст
  67. ↑ Ошибка цитирования Неверный тег <ref>; для сносок sand2012 не указан текст
  68. ↑ Ошибка цитирования Неверный тег <ref>; для сносок safi2007 не указан текст
  69. ↑ Ошибка цитирования Неверный тег <ref>; для сносок gutr2006 не указан текст
  70. ↑ Ошибка цитирования Неверный тег <ref>; для сносок zimm2006 не указан текст
  71. ↑ Ошибка цитирования Неверный тег <ref>; для сносок betaxxxx не указан текст
  72. ↑ Ошибка цитирования Неверный тег <ref>; для сносок reim2006 не указан текст
  73. ↑ Ошибка цитирования Неверный тег <ref>; для сносок wdc2010 не указан текст
  74. ↑ Ошибка цитирования Неверный тег <ref>; для сносок bask2006 не указан текст
  75. ↑ Ошибка цитирования Неверный тег <ref>; для сносок seagb2011 не указан текст
  76. ↑ Ошибка цитирования Неверный тег <ref>; для сносок suitbxxxx не указан текст
  77. ↑ Ошибка цитирования Неверный тег <ref>; для сносок iucr1995 не указан текст
  78. ↑ Ошибка цитирования Неверный тег <ref>; для сносок iucr1996 не указан текст
  79. ↑ Ошибка цитирования Неверный тег <ref>; для сносок iec1999 не указан текст
  80. ↑ Ошибка цитирования Неверный тег <ref>; для сносок iucr1999 не указан текст
  81. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IEC2000 не указан текст
  82. ↑ Ошибка цитирования Неверный тег <ref>; для сносок iec2005 не указан текст
  83. ↑ Ошибка цитирования Неверный тег <ref>; для сносок niso2008 не указан текст
  84. ↑ Ошибка цитирования Неверный тег <ref>; для сносок jcgm2012 не указан текст
  85. ↑ Ошибка цитирования Неверный тег <ref>; для сносок barr1997 не указан текст
  86. ↑ Ошибка цитирования Неверный тег <ref>; для сносок NISTbin не указан текст
  87. ↑ Ошибка цитирования Неверный тег <ref>; для сносок taylo2008 не указан текст
  88. ↑ Ошибка цитирования Неверный тег <ref>; для сносок jedec2021 не указан текст
  89. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC2014 не указан текст
  90. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IEEE2003 не указан текст
  91. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IEEE2005 не указан текст
  92. ↑ Ошибка цитирования Неверный тег <ref>; для сносок walli2008 не указан текст
  93. ↑ Шаблон:Cite journal "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.
  94. ↑ Ошибка цитирования Неверный тег <ref>; для сносок BIPM8web не указан текст
  95. ↑ Ошибка цитирования Неверный тег <ref>; для сносок SAE2017 не указан текст
  96. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CENELEC2003 не указан текст
  97. ↑ Ошибка цитирования Неверный тег <ref>; для сносок CENELECxxxx не указан текст
  98. ↑ Ошибка цитирования Неверный тег <ref>; для сносок hpen2009 не указан текст
  99. ↑ Ошибка цитирования Неверный тег <ref>; для сносок resp2011 не указан текст
  100. ↑ Ошибка цитирования Неверный тег <ref>; для сносок IBMaxxxx не указан текст
  101. ↑ Ошибка цитирования Неверный тег <ref>; для сносок customxxxx не указан текст
  102. ↑ Ошибка цитирования Неверный тег <ref>; для сносок HP2012 не указан текст
  103. ↑ Ошибка цитирования Неверный тег <ref>; для сносок sony2017 не указан текст
  104. ↑ Ошибка цитирования Неверный тег <ref>; для сносок forall2012 не указан текст
  105. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-terms не указан текст
  106. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-ddr3 не указан текст
  107. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-ddr2 не указан текст
  108. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-configs не указан текст
  109. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-configs-toc не указан текст
  110. ↑ Ошибка цитирования Неверный тег <ref>; для сносок JEDEC-configs-terms не указан текст
  111. ↑ Ошибка цитирования Неверный тег <ref>; для сносок hita2009 не указан текст
  112. ↑ Ошибка цитирования Неверный тег <ref>; для сносок sams2011 не указан текст
  113. ↑ Ошибка цитирования Неверный тег <ref>; для сносок seag2017 не указан текст
  114. ↑ Ошибка цитирования Неверный тег <ref>; для сносок toshi2009 не указан текст
  115. ↑ Ошибка цитирования Неверный тег <ref>; для сносок WDC2005 не указан текст
  116. ↑ Ошибка цитирования Неверный тег <ref>; для сносок toshi2017 не указан текст
  117. ↑ Ошибка цитирования Неверный тег <ref>; для сносок linux2001 не указан текст
  118. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ESR2012 не указан текст
  119. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ubuntu2012 не указан текст
  120. ↑ Ошибка цитирования Неверный тег <ref>; для сносок ubuntu2012b не указан текст
  121. ↑ Ошибка цитирования Неверный тег <ref>; для сносок snow2009 не указан текст
  122. ↑ Ошибка цитирования Неверный тег <ref>; для сносок apple2018 не указан текст
Источник — http://wikihandbk.com/ruwiki/index.php?title=Английская_Википедия:Binary_prefix&oldid=13528159