From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Heikki Orsila <shdl@zakalwe.fi>, Bodo Eggert <7eggert@gmx.de>,
Tony Foiani <tkil@scrye.com>,
Leon Woestenberg <leon.woestenberg@gmail.com>,
linux-kernel@vger.kernel.org,
David Schwartz <davids@webmaster.com>
Subject: Re: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)
Date: Mon, 22 Jan 2007 02:56:37 +0100 [thread overview]
Message-ID: <m38xfvrfhm.fsf@maximus.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0701212223340.29213@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Sun, 21 Jan 2007 22:27:11 +0100 (MET)")
Jan Engelhardt <jengelh@linux01.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
next prev parent reply other threads:[~2007-01-22 1:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7FsPf-51s-9@gated-at.bofh.it>
[not found] ` <7FxlV-3sb-1@gated-at.bofh.it>
[not found] ` <7FyUF-5XD-21@gated-at.bofh.it>
2007-01-21 10:40 ` PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2) Bodo Eggert
2007-01-21 11:10 ` Eduard Bloch
2007-01-21 22:08 ` Stefan Richter
2007-01-22 15:53 ` Lennart Sorensen
2007-01-22 16:58 ` Jan Engelhardt
2007-01-22 18:36 ` Alan
2007-01-22 19:24 ` Tony Foiani
2007-01-22 22:26 ` Bodo Eggert
2007-01-22 20:44 ` Lennart Sorensen
2007-01-22 21:17 ` linux-os (Dick Johnson)
2007-01-22 20:43 ` Lennart Sorensen
2007-01-22 21:22 ` Jan Engelhardt
2007-01-21 14:45 ` Benny Amorsen
2007-01-21 15:06 ` Heikki Orsila
2007-01-21 21:27 ` Jan Engelhardt
2007-01-22 1:56 ` Krzysztof Halasa [this message]
2007-01-22 10:39 ` Bernd Petrovitsch
2007-01-22 10:48 ` Andreas Schwab
2007-01-23 1:04 ` Krzysztof Halasa
2007-01-23 1:45 ` Jan Engelhardt
2007-01-23 9:23 ` Andreas Schwab
2007-01-23 13:14 ` Krzysztof Halasa
2007-01-20 8:08 Michał Kudła
2007-01-20 10:29 ` David Schwartz
2007-01-20 18:07 ` Leon Woestenberg
2007-01-20 22:54 ` David Schwartz
2007-01-21 0:07 ` Tony Foiani
2007-01-21 21:12 ` Jan Engelhardt
2007-01-22 6:45 ` Tony Foiani
2007-01-22 8:25 ` Roland Kuhn
2007-01-22 15:43 ` Lennart Sorensen
2007-01-21 7:11 ` H. Peter Anvin
2007-01-21 20:03 ` Geert Uytterhoeven
2007-01-21 20:06 ` H. Peter Anvin
2007-01-21 17:04 ` Leon Woestenberg
2007-01-21 22:12 ` David Schwartz
2007-01-22 8:49 ` Benny Amorsen
2007-01-27 15:06 ` Andries Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38xfvrfhm.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=7eggert@gmx.de \
--cc=davids@webmaster.com \
--cc=jengelh@linux01.gwdg.de \
--cc=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shdl@zakalwe.fi \
--cc=tkil@scrye.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.