From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alex Q Chen <aqchen@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Minor numbers
Date: Mon, 14 May 2001 15:02:08 +0200 (MEST) [thread overview]
Message-ID: <200105141302.PAA14005@cave.bitwizard.nl> (raw)
In-Reply-To: <E14zDcI-0007TB-00@the-village.bc.nu> from Alan Cox at "May 14, 2001 09:22:09 am"
Alan Cox wrote:
> > 255. Has this limitation been some how addressed with 2.4? 256 devices
> > per module, sometimes is not enough, especially if you are in the SAN
> > environment; or when the 256 minors numbers are broken down to several
>
> 2.4 is using 16bit dev_t in kernel still. Application space sees a much
> larger dev_t so we can make the move in 2.5 very easily
>
> > work-around or is proposing a solution? I believe that minor and major
> > numbers for SUN and AIX are both 16 bits each (32 bits dev_t).
>
> 20:12 is more common
Which is major, which is minor?
I have one (private) driver that requires around 5000 minors.
(currently through some 20 majors) (Currently only just over half of
these are physically installed....)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-05-14 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 1:28 Minor numbers Alex Q Chen
2001-05-14 8:22 ` Alan Cox
2001-05-14 13:02 ` Rogier Wolff [this message]
2001-05-14 14:57 ` Alan Cox
2001-05-14 16:02 ` H. Peter Anvin
2001-05-14 17:13 ` Joel Becker
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 16:53 Andries.Brouwer
2001-05-14 16:57 ` Alan Cox
2001-05-14 17:05 Andries.Brouwer
2001-05-14 17:04 ` Alan Cox
2001-05-14 18:09 Andries.Brouwer
2001-05-14 20:06 ` Alan Cox
2001-05-14 21:05 Andries.Brouwer
2002-11-01 15:40 Minor Numbers sah
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=200105141302.PAA14005@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aqchen@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox