All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: R.E.Wolff@bitwizard.nl, alan@lxorguk.ukuu.org.uk
Cc: aqchen@us.ibm.com, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Minor numbers
Date: Mon, 14 May 2001 18:53:05 +0200 (MET DST)	[thread overview]
Message-ID: <UTC200105141653.SAA09595.aeb@vlet.cwi.nl> (raw)

>>> 20:12 is more common

>> Which is major, which is minor?

> 20bit major

That is not more common. Around us we see major:minor splits
8:24, 12:20, 14:18. If we want to use NFSv3 and communicate
with all these systems we would do wise to use 32:32.

[Reminds me of a discussion that ended unfinished.
Stage 1: "64 bits? Never in hell!"
Answer 1: These 64 bits do not make the kernel slow.
  Indeed, the kernel uses a 32-bit pointer.
Stage 2: "but I am on a holy crusade"
Answer 2: These bits are not about bloat but about the width of
  the communication channel between user space and filesystem.
Stage 3: <silence so far>
Wonder whether Linus still objects. Let me cc him.]

Andries

             reply	other threads:[~2001-05-14 16:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 16:53 Andries.Brouwer [this message]
2001-05-14 16:57 ` Minor numbers Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01 15:40 Minor Numbers sah
2001-05-14 21:05 Minor numbers Andries.Brouwer
2001-05-14 18:09 Andries.Brouwer
2001-05-14 20:06 ` Alan Cox
2001-05-14 17:05 Andries.Brouwer
2001-05-14 17:04 ` Alan Cox
2001-05-14  1:28 Alex Q Chen
2001-05-14  8:22 ` Alan Cox
2001-05-14 13:02   ` Rogier Wolff
2001-05-14 14:57     ` Alan Cox
2001-05-14 16:02       ` H. Peter Anvin
2001-05-14 17:13       ` Joel Becker

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=UTC200105141653.SAA09595.aeb@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=R.E.Wolff@bitwizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=aqchen@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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.