From: Patrick Mansfield <patmans@us.ibm.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Douglas Gilbert <dougg@torque.net>,
James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
pbadari@us.ibm.com
Subject: Re: 2.6.0 stability and the BK scsi trees
Date: Sat, 18 Oct 2003 08:24:50 -0700 [thread overview]
Message-ID: <20031018082450.A6510@beaverton.ibm.com> (raw)
In-Reply-To: <20031016132804.GA18370@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Thu, Oct 16, 2003 at 02:28:04PM +0100
On Thu, Oct 16, 2003 at 02:28:04PM +0100, Matthew Wilcox wrote:
> On Thu, Oct 16, 2003 at 09:56:54PM +1000, Douglas Gilbert wrote:
> > What was the point of putting 32 dev_t's into the
> > kernel? Many people who were advocating it used
> > the increased number of scsi disks (> 256) and
> > partitions (from 15 to 63 [to match the ide subsystem])
> > as a major reason.
> >
> > The sd driver is still littered with hacks to distribute
> > its 256 (max) disks over 8 majors. Shouldn't this be
> > fixed?
>
> Well, let's see some fixes and then decide whether it's worth merging
> before 2.6.0 or after 2.6.0. We can be sure that vendors will integrate
> this patch even if it's not in mainline kernel.org ... and i'd rather
> see one variant of the patch which everybody uses than a different one
> in RH, SuSE and Linux 2.7.
If you have not seen it, Badari's sd patch is in the mm tree:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test7/2.6.0-test7-mm1/broken-out/support-zillions-of-scsi-disks.patch
-- Patrick Mansfield
next prev parent reply other threads:[~2003-10-18 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 0:59 2.6.0 stability and the BK scsi trees James Bottomley
2003-10-16 11:56 ` Douglas Gilbert
2003-10-16 13:28 ` Matthew Wilcox
2003-10-18 15:24 ` Patrick Mansfield [this message]
2003-10-18 16:38 ` Matthew Wilcox
2003-10-20 14:54 ` Badari Pulavarty
2003-10-17 12:31 ` Christoph Hellwig
2003-10-22 14:23 ` James Bottomley
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=20031018082450.A6510@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=willy@debian.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.