From: badari <pbadari@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org,
"viro@parcelfarce.linux.theplanet.co.uk"
<viro@parcelfarce.linux.theplanet.co.uk>
Subject: Re: many-disk support
Date: Fri, 09 Jan 2004 10:51:30 -0800 [thread overview]
Message-ID: <3FFEF832.A7DB3D92@us.ibm.com> (raw)
In-Reply-To: 20031229110603.A27408@infradead.org
I am not sorry for not replying for so long. I have been on vacation.
1) I am not really concerned about bitmap overhead. Bitmap of one
page (4k) - should be enough to support 32K disks. That should be
good enough for most of the machines.
2) I used config option for 2 reasons
- to minimize impact on machines this is not needed.
- didn't want to depend on <major, minor> split to decide on
how many disks we can support.
3) The reason, I assigned all the disks to last major is to maintain backward
compatibility with current major, minor assignments. Hopefully "udev"
will cleanup all these.
My question is, what do we do for current 2.6 ? Hoping to address these
before distros start making 2.6 distros and adding their own stuff to support
this.
And also, is there a plan to support more partitions per disk ?
Thanks,
Badari
Christoph Hellwig wrote:
> On Mon, Dec 29, 2003 at 02:25:49AM -0800, Andrew Morton wrote:
> > Guys, I've had this patch for ages. Badari seemed to say that it wasn't
> > the "right" way to do it.
> >
> > Can we get this nailed down please?
>
> - I think the bitmap overhead was killing us on big x86 machines, right?
> so that might need some swork.
> - a config option definitly is the wrong way to go.
> - I don't think assigning more numbers to the last major is a bad idea,
> better assign them to the first one, maybe with a hole for what we're
> using the other majors currently for, so when udev gets more mature
> we can kill the additional majors.
prev parent reply other threads:[~2004-01-09 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 10:25 many-disk support Andrew Morton
2003-12-29 11:06 ` Christoph Hellwig
2003-12-29 14:27 ` Matthew Wilcox
2004-01-09 18:51 ` badari [this message]
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=3FFEF832.A7DB3D92@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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