From: Christoph Hellwig <hch@infradead.org>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Kurt Garloff <kurt@garloff.de>,
Douglas Gilbert <dougg@torque.net>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: Fwd: 32bit dev_t
Date: Mon, 27 Jan 2003 22:51:25 +0000 [thread overview]
Message-ID: <20030127225125.A13617@infradead.org> (raw)
In-Reply-To: <20030124182952.GF20972@ca-server1.us.oracle.com>; from Joel.Becker@oracle.com on Fri, Jan 24, 2003 at 10:29:53AM -0800
On Fri, Jan 24, 2003 at 10:29:53AM -0800, Joel Becker wrote:
> How are they allocated? Is this dynamic, or compiled in? In
> addition, what is the maximum amount? If it's less than 1000 disks,
> it's too small for today. If it's less than 2000 disks, it's probably
> too small for 2.6's lifetime.
Currently it's compiled in, and the trivial change to make it use
register_blkdev with a 0 major argument until all globally unused majors
are gone is left to the reader..
next prev parent reply other threads:[~2003-01-27 22:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 21:56 Fwd: 32bit dev_t Douglas Gilbert
2003-01-22 17:18 ` Patrick Mansfield
2003-01-22 23:55 ` Tim Pepper
2003-01-23 0:51 ` Joel Becker
2003-01-23 18:31 ` Kurt Garloff
2003-01-23 22:18 ` Christoph Hellwig
2003-01-24 8:20 ` Kurt Garloff
2003-01-24 18:29 ` Joel Becker
2003-01-27 22:51 ` Christoph Hellwig [this message]
2003-01-28 11:21 ` Alan Cox
2003-01-28 11:28 ` Christoph Hellwig
2003-01-28 15:19 ` Kurt Garloff
2003-01-28 16:33 ` Bryan Henderson
2003-01-28 18:22 ` Alan Cox
2003-01-28 17:09 ` New model for managing dev_t's for partitionable block devices Steven Dake
2003-01-29 1:41 ` Bryan Henderson
2003-01-29 16:45 ` Steven Dake
2003-01-29 17:38 ` Andries Brouwer
2003-01-29 18:00 ` Kurt Garloff
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=20030127225125.A13617@infradead.org \
--to=hch@infradead.org \
--cc=Joel.Becker@oracle.com \
--cc=dougg@torque.net \
--cc=kurt@garloff.de \
--cc=linux-scsi@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