From: Joel Becker <Joel.Becker@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
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: Fri, 24 Jan 2003 10:29:53 -0800 [thread overview]
Message-ID: <20030124182952.GF20972@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20030123221805.A2468@infradead.org>
On Thu, Jan 23, 2003 at 10:18:05PM +0000, Christoph Hellwig wrote:
> the Linux 2.5 sd and sr drivers are only limited by the number of majors
> allocated to them. There's no more architectural limit or any global
> array.
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.
Joel
--
"Practice random acts of kindness and senseless acts of beauty."
Oh, and don't forget where your towel is.
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2003-01-24 18:30 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 [this message]
2003-01-27 22:51 ` Christoph Hellwig
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=20030124182952.GF20972@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=dougg@torque.net \
--cc=hch@infradead.org \
--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