From: Douglas Gilbert <dougg@torque.net>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.0 stability and the BK scsi trees
Date: Thu, 16 Oct 2003 21:56:54 +1000 [thread overview]
Message-ID: <3F8E8786.2020502@torque.net> (raw)
In-Reply-To: <1066265974.16761.426.camel@fuzzy>
James Bottomley wrote:
> In the light of the recently announced "bug fixes only" edict for the
> 2.6 kernel, I'll be splitting our current SCSI BK tree:
Ok, I'll bite:-)
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?
Comments?
Doug Gilbert
next prev parent reply other threads:[~2003-10-16 11:57 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 [this message]
2003-10-16 13:28 ` Matthew Wilcox
2003-10-18 15:24 ` Patrick Mansfield
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=3F8E8786.2020502@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--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 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.