linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: nick@guardiandigital.com, linux-kernel@vger.kernel.org
Subject: units - was: Re: Determining maximum partition size...
Date: Tue, 28 Aug 2001 23:45:21 +0200	[thread overview]
Message-ID: <20010828234521.A20830@win.tue.nl> (raw)
In-Reply-To: <3B82BCCB.377BCC4@guardiandigital.com> <3B82BCCB.377BCC4@guardiandigital.com> <20010828142315.A20775@win.tue.nl> <5.1.0.14.2.20010828134152.04eeaa10@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20010828134152.04eeaa10@pop.cus.cam.ac.uk>; from Anton Altaparmakov on Tue, Aug 28, 2001 at 01:53:29PM +0100

On Tue, Aug 28, 2001 at 01:53:29PM +0100, Anton Altaparmakov wrote:

> > > I thought maybe Linux set 1MB=1000k but that doesn't seem to case.

> >Well, 1 M = 1000 k by definition of the SI system of units.
> >This has nothing to do with Linux.
> 
> While it is true that M = 10^6 and k = 10^3, surely that doesn't apply to 
> byte quantities?!? At least I have always interpreted 1 Megabyte = 1024 
> kilobytes = 1024*1024 bytes


Ah, an old discussion - I imagine it must have occurred here a few times.
Anyway: k is the prefix for 1000, M is the prefix for 1000000. Always.

But there is a natural sloppiness, where people round numbers when either
the precise size is unimportant, or is clear from the context.
If xyzzies come in boxes of 27 and I say that I bought a hundred xyzzies
then that probably means that in fact I bought 108.

Thus, our old PDP8 with 4k of memory had 4096 12-bit words, that is,
6 KiB in modern terminology.

You see two very different situations here: "precise size is unimportant"
and "precise size is clear from the context". When someone says that she
bought a 10 GB disk I will assume that the precise size is somewhere
between 9.5 and 10.5 GB. This is the "rounded" case.
When someone says that she bought a 32 MB SIMM I will assume that this was
32 MiB, that is, 2^25 bytes, since, unlike disks, memory modules tend to
come in power-of-two units. This is the "clear from the context" case.

Andries

      reply	other threads:[~2001-08-28 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 19:55 Determining maximum partition size on a hard disk Nick DeClario
2001-08-28 12:23 ` Guest section DW
2001-08-28 12:53 ` Anton Altaparmakov
2001-08-28 21:45   ` Guest section DW [this message]

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=20010828234521.A20830@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@guardiandigital.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).