All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)
Date: Sun, 21 Jan 2007 14:12:26 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKEENPBAAC.davids@webmaster.com> (raw)
In-Reply-To: <c384c5ea0701210904t15f44178hfd807b4553e0e3d3@mail.gmail.com>


> > Talk about a cure worse than the disease! So you're
> > saying that 256MB flash
> > cards could be advertised as having 268.4MB? A 512MB RAM stick is
> > mislabelled and could correctly say 536.8MB? That's just plain
> > craziness.

> No, I meant to advertise it as a 256 MiB flash device and a 512 MiB
> flash device, as the Mi prefix has a single interpretation, that is 2
> to the power of 20, as per IEC 60027-2, whereas M has not if used
> outside SI units.

If it actually has 256*2^20 bytes, why advertise it as "256 MiB" when "268.4
MB" is equally valid and looks better? It really comes down to this: is it
your position that "256 MB" can only correctly mean 256 million bytes?

If you are right, a "512MB" RAM stick is mislabelled and is more correctly
labelled as "536.8MB". (With 512MiB being equally correct.)

Isn't that obviously not just wrong but borderline crazy? Yes, your position
has some nice consequences, but that doesn't allow you to ignore the bad
ones.

Unfortunately, we're not writing on a clean slate here.

DS



  reply	other threads:[~2007-01-21 22:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20  8:08 PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2) 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 [this message]
2007-01-22  8:49           ` Benny Amorsen
2007-01-27 15:06 ` Andries Brouwer
     [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     ` 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
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

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=MDEHLPKNGKAHNMBLJOLKEENPBAAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.