9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Rstat needs three size fields?
Date: Tue,  8 Jul 2003 08:32:01 +0000	[thread overview]
Message-ID: <3F09EDB7.626FE4F5@null.net> (raw)
In-Reply-To: <0ecb9b15ba9f3534a79e8cc3e4f4cc2c@mightycheese.com>

"rob pike, esq." wrote:
> >> 65536 is not a very big number in modern i/o systems.
> > Actally neither is 2^32.
> sometimes you become boyd-like in your contrarianism.
> 2^32 is a huge block size, even today, while 2^16 is not.

Perhaps I'm getting tired of engineers always tweaking
size fields up by a small amount every time they become
too small.  If you've had to deal with large IDE drives
on BIOSes more than a couple of years old you know what
I mean.  Ever-increasing-size FAT filesystem formats are
another example.  Utility software that is even slightly
old keeps turning out to be unable to cope with new
developments, due mainly to inadequate bits in existing
formats.  Why should there be such a drain on developer
resources to continually adapt to changing formats when
we could do it right for once and for all?

My rule of thumb used to be that whatever the biggest
size you can imagine for some object, allocate twice
as many bits to hold its size as seem sufficient.  But
even that approach doesn't survive for the decades that
ought to be attainable for things like disk descriptors.


  parent reply	other threads:[~2003-07-08  8:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 18:04 Sam
2003-06-30 19:08 ` ron minnich
2003-06-30 19:15   ` boyd, rounin
2003-07-04  3:18 ` Russ Cox
2003-07-04 15:04   ` Sam
2003-07-04 17:13     ` rob pike, esq.
2003-07-07  8:33       ` Douglas A. Gwyn
2003-07-07  9:03         ` Geoff Collyer
2003-07-07 15:10           ` Douglas A. Gwyn
2003-07-08  0:49             ` ron minnich
2003-07-07 15:50           ` rob pike, esq.
2003-07-07 20:38             ` boyd, rounin
2003-07-07 21:18               ` rog
2003-07-07 21:28                 ` boyd, rounin
2003-07-07 23:23                   ` [9fans] simple, sufficient rog
2003-07-07 20:54             ` [9fans] Rstat needs three size fields? Geoff Collyer
2003-07-09  2:07           ` William Josephson
2003-07-07 15:48         ` rob pike, esq.
2003-07-07 15:58           ` Jack Johnson
2003-07-08  8:32           ` Douglas A. Gwyn [this message]
2003-07-08 10:30             ` boyd, rounin
2003-07-08 11:09               ` matt
2003-07-08 11:36                 ` Dan Cross
2003-07-08 12:12                   ` boyd, rounin
2003-07-08 14:14                     ` ron minnich
2003-07-08 17:42                 ` chris
2003-07-08 20:19                   ` matt
2003-07-08 20:41                     ` boyd, rounin
2003-07-09 14:58                       ` rog
2003-07-09 19:42                         ` boyd, rounin
2003-07-10 12:30                           ` rog
2003-07-08 22:09                   ` ron minnich
2003-07-08 22:19                     ` Dan Cross
2003-07-09  1:27                       ` ron minnich
2003-07-01 21:46 boyd, rounin
2003-07-02  0:24 boyd, rounin

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=3F09EDB7.626FE4F5@null.net \
    --to=dagwyn@null.net \
    --cc=9fans@cse.psu.edu \
    /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).