1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 31/03/14 01:27 PM, Rich Freeman wrote: |
5 |
> On Mon, Mar 31, 2014 at 11:44 AM, Michał Górny <mgorny@g.o> |
6 |
> wrote: |
7 |
>> Dnia 2014-03-31, o godz. 06:56:19 Joshua Kinard |
8 |
>> <kumba@g.o> napisał(a): |
9 |
>>>> |
10 |
>>> In some respect, if all one cares about is free space on a disk |
11 |
>>> drive or how fast they can stream a movie, then the KiB/MiB |
12 |
>>> thing works. But if you play with bits and bytes from |
13 |
>>> time-to-time (and worry about byte alignment) or sometimes |
14 |
>>> fiddle w/ partition tables in a hex editor...you're going to |
15 |
>>> think in terms of powers of two. |
16 |
> |
17 |
> KiB/MiB ARE powers of two. It is KB/MB which are powers of ten |
18 |
> (depending on who you talk to). |
19 |
> |
20 |
> Drive sizes tend to be reported in MB/GB, and memory tends to be |
21 |
> reported in MiB, GiB (though they may or may not use those |
22 |
> abbreviations when doing so). |
23 |
> |
24 |
|
25 |
This is very much old "standard" vs new standard in terms of naming. |
26 |
For those of us that have been around long enough, Mega/Kilo/etc have |
27 |
always meant 1024 when addressing computational storage, as per for |
28 |
instance ANSI/IEEE Std 1084-1986. However, as people know this did |
29 |
become (or has always been) used ambiguously and so these terms were |
30 |
apparently deprecated in favour of MiB, KiB etc by the IEC starting at |
31 |
around 1996 and with formal adoption 1999 with IEC 60027-2 Amendment 2 |
32 |
(and expanded adoption in ISO/IEC IEC 80000-13:2008) |
33 |
|
34 |
[*] source: http://en.wikipedia.org/wiki/Binary_prefix |
35 |
|
36 |
+1 for usage of {K,M,G,T,...}iB as per standard. |
37 |
|
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v2.0.22 (GNU/Linux) |
40 |
|
41 |
iF4EAREIAAYFAlM5rGkACgkQ2ugaI38ACPAM2QD/eNQIRbUTfrGAolqbCPR6fR83 |
42 |
Is+jgG1MClaBeBki3aoBAJVluP0Gq4fWNVdm7Dl0OoT4tL7JIMjadRCO34mn/mmn |
43 |
=KM13 |
44 |
-----END PGP SIGNATURE----- |