From: Badari Pulavarty <pbadari@us.ibm.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Matthew Wilcox <willy@debian.org>,
Douglas Gilbert <dougg@torque.net>,
James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.0 stability and the BK scsi trees
Date: Mon, 20 Oct 2003 07:54:21 -0700 [thread overview]
Message-ID: <200310200754.21984.pbadari@us.ibm.com> (raw)
In-Reply-To: <20031018163820.GC18370@parcelfarce.linux.theplanet.co.uk>
On Saturday 18 October 2003 09:38 am, Matthew Wilcox wrote:
> On Sat, Oct 18, 2003 at 08:24:50AM -0700, Patrick Mansfield wrote:
> > 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
>
> I hadn't ... it doesn't address expanding the number of partitions or
> the problem that the sd_index_bits array will grow to a huge size.
Yes. I did not want to address expanding the number of partitions issue -
since there is no resolution on it. (to be frank, I am not really interested
in it - so never looked at).
I address sd_index_bits array problem in a crude way. I made the max number
of disks to support as configurable.
I wanted to make the patch really simple - so that we can make few
decisions before making too many changes.
All I wanted to do was following:
- support > 256 scsi disks
- for now, maintain backward compatibility with current /dev major/minor
assignments
- test out any kernel (lowmem bloating) issues.
Thanks,
Badari
next prev parent reply other threads:[~2003-10-20 14:58 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
2003-10-18 16:38 ` Matthew Wilcox
2003-10-20 14:54 ` Badari Pulavarty [this message]
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=200310200754.21984.pbadari@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox