| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <m38xfvrfhm.fsf@maximus.localdomain> Date: Mon, 22 Jan 2007 02:56:37 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Jan Engelhardt <jengelh@...ux01.gwdg.de> Cc: Heikki Orsila <shdl@...alwe.fi>, Bodo Eggert <7eggert@....de>, Tony Foiani <tkil@...ye.com>, Leon Woestenberg <leon.woestenberg@...il.com>, linux-kernel@...r.kernel.org, David Schwartz <davids@...master.com> Subject: Re: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2) Jan Engelhardt <jengelh@...ux01.gwdg.de> writes: > Bleh. Except for storage, base 1024 was used for almost everything > I remember. 4 MB memory meant 4096 KB, and that's still the case today. > Most likely the same for transfer rates. Nope, transfer rates were initially 1000-based: 9.6 kbps = 9600 bps, 28.8 kbps = 28800 bps, 64 kbps = 64000 bps. Then it went 128, 256, 512 kbps = 512000 bps and 1 Mbps = 2 * 512 kbps = 1024000 bps. But it's limited mostly to serial interfaces. Other networks use 10, 1000 etc. because they have nothing natural in (powers of) 2 so 1 Mbps may be 1000000 bps as well. > It's just that storage vendors broke the computer rule and went with 1000. 1024 etc. is (should be) natural to disks because the sector size is 512 B, 2048 B or something like that. -- Krzysztof Halasa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists