From: Jeff Garzik <jgarzik@pobox.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Steven Dake <sdake@mvista.com>, linux-kernel@vger.kernel.org
Subject: Re: 32bit dev_t
Date: Tue, 21 Jan 2003 17:21:01 -0500 [thread overview]
Message-ID: <20030121222101.GA1353@gtf.org> (raw)
In-Reply-To: <20030121215602.GI20972@ca-server1.us.oracle.com>
On Tue, Jan 21, 2003 at 01:56:02PM -0800, Joel Becker wrote:
> On Tue, Jan 21, 2003 at 02:29:17PM -0700, Steven Dake wrote:
> > Linux doesn't really need a 32 bit kdev_t structure to support 1000
> > disks. There is plenty of device space available to support over 1500
> > disks by modifying the linux scsi layer.
>
> First, that's an approach that removes space from other devices.
> In addition, I suspect we'll see 2000 disk systems before we see 2.8.
Of course, we know the solution is /dev/disk, as mentioned by Linus at
least a couple times, which eliminates a lot of dev_t limitation
issues... :)
Jeff
next prev parent reply other threads:[~2003-01-21 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 19:50 32bit dev_t Joel Becker
2003-01-21 21:29 ` Steven Dake
2003-01-21 21:56 ` Joel Becker
2003-01-21 22:21 ` Jeff Garzik [this message]
2003-01-21 22:33 ` Alan
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 22:04 Andries.Brouwer
2003-01-25 1:51 ` Joel Becker
2003-02-03 18:21 ` H. Peter Anvin
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=20030121222101.GA1353@gtf.org \
--to=jgarzik@pobox.com \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sdake@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox