All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Q Chen" <aqchen@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Minor numbers
Date: Sun, 13 May 2001 18:28:46 -0700	[thread overview]
Message-ID: <OF2C42607E.899F4413-ON87256A4C.00068D2E@LocalDomain> (raw)

To the best of my knowledge, dev_t number is still 16 bits with 8 most
significant bits being the major number and the other 8 bits being the
minor number; which of course means that minor numbers can only go up to
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
ranges of numbers to address different types of special files.  I don't see
how this problem can be solved with dev_fs either.  Anyone out there with a
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).

Thanks in advance for your input.

Thanks!

Sincerely,
Alex Chen

IBM SSD Device Driver Development
Office: 9000 S. Rita Rd 9032/2262
Email: aqchen@us.ibm.com
Phone: (external) 520-799-5212 (Tie Line) (321)-5212


             reply	other threads:[~2001-05-14  1:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14  1:28 Alex Q Chen [this message]
2001-05-14  8:22 ` Minor numbers 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
  -- 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=OF2C42607E.899F4413-ON87256A4C.00068D2E@LocalDomain \
    --to=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 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.