From: Steven Dake <sdake@mvista.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 32bit dev_t
Date: Tue, 21 Jan 2003 14:29:17 -0700 [thread overview]
Message-ID: <3E2DBBAD.80206@mvista.com> (raw)
In-Reply-To: <20030121195041.GE20972@ca-server1.us.oracle.com>
Joel,
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.
Thanks
-steve
Joel Becker wrote:
>Folks,
> Who is tracking the 32bit dev_t effort for 2.5? There are
>already existing installations with 500 to 1000 disks attached to a
>system, and I don't know that Linux really wants to wait four years to
>get there!
> If someone could point me to a current patch or any current
>information about the issues, I'd really appreciate it.
>
>Joel
>
>
>
next prev parent reply other threads:[~2003-01-21 21:23 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 [this message]
2003-01-21 21:56 ` Joel Becker
2003-01-21 22:21 ` Jeff Garzik
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=3E2DBBAD.80206@mvista.com \
--to=sdake@mvista.com \
--cc=Joel.Becker@oracle.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.