From: Andreas Dilger <adilger@clusterfs.com>
To: Kurt Garloff <garloff@suse.de>,
Alexander Viro <viro@math.psu.edu>,
Linux SCSI list <linux-scsi@vger.kernel.org>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] sd_many done right (1/5)
Date: Fri, 26 Jul 2002 11:50:27 -0600 [thread overview]
Message-ID: <20020726175027.GC2746@clusterfs.com> (raw)
In-Reply-To: <20020726165411.GI19721@nbkurt.etpnet.phys.tue.nl>
On Jul 26, 2002 18:54 +0200, Kurt Garloff wrote:
> On Fri, Jul 26, 2002 at 12:45:41PM -0400, Alexander Viro wrote:
> > On Fri, 26 Jul 2002, Kurt Garloff wrote:
> > > The patches are all available at
> > > http://www.suse.de/~garloff/linux/scsi-many/
> >
> > As long as you realize that it won't go in 2.5 in that form...
>
> The sd parts can and should be ported to 2.5, I think.
> The /proc/scsi/scsi extensions and other stuff I wrote to support it,
> won't be needed, as we have driverfs in 2.5.
> And, of course, the device number management will be solved in a more
> general way, but I do not yet see how.
Actually, one interesting aspect of the EVMS vs. device-mapper argument
going on that has totally been missed is that EVMS can do management of
ALL disk block devices.
At startup time it "consumes" all of the disk block devices in order to
generate the various mappings (LVM, RAID, etc) and at the end it spits
out the resulting devices as EVMS major devices. This includes devices
that have not been remapped, like hdXY or sdMN. EVMS has facilities
to ensure that devices get repeatable major/minor numbers if needed,
but they are allocated on an as-needed basis.
Currently EVMS only has a single major number, but it is my understanding
that they could easily take over all of the IDE and SCSI major numbers.
We would not have to worry about sparse device number allocation anymore,
and could have thousands of disks/partitions without any problems.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-07-26 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 15:45 [PATCH] sd_many done right (1/5) Kurt Garloff
2002-07-26 16:45 ` Alexander Viro
2002-07-26 16:54 ` Kurt Garloff
2002-07-26 17:50 ` Andreas Dilger [this message]
2002-07-26 17:55 ` Christoph Hellwig
2002-07-26 17:55 ` Christoph Hellwig
2002-07-26 22:32 ` Kurt Garloff
2002-07-27 9:41 ` Christoph Hellwig
2002-07-28 0:42 ` Kurt Garloff
2002-07-26 22:32 ` Kurt Garloff
2002-07-26 23:28 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-07-26 15:45 Kurt Garloff
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=20020726175027.GC2746@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=viro@math.psu.edu \
/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.