From: Kevin Corry <corryk@us.ibm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: EVMS Submission for 2.5
Date: Wed, 2 Oct 2002 17:03:19 -0500 [thread overview]
Message-ID: <02100217031903.18102@boiler> (raw)
In-Reply-To: <Pine.GSO.4.21.0210021812590.9782-100000@weyl.math.psu.edu>
On Wednesday 02 October 2002 17:14, Alexander Viro wrote:
> On Wed, 2 Oct 2002, Kevin Corry wrote:
> > On behalf of the EVMS team, I'd like to submit the Enterprise Volume
> > Management System for inclusion in the 2.5 Linux kernel tree.
> >
> > To make this as simple as possible for you, there is a Bitkeeper
> > tree available with the latest EVMS source code, located at:
> > http://evms.bkbits.net/linux-2.5
> > This tree is sync'd with the linux-2.5 tree on linux.bkbits.net
> > as of about noon today (Oct 2).
> >
> > - Add a function, walk_gendisk(), to drivers/block/genhd.c to allow
> > EVMS to get information about the disks on the system from the
> > gendisk list in a safe manner.
>
> Consider that one vetoed. Linus, please do _not_ apply until that
> stuff is resolved - it conflicts with a bunch of cleanups we'll
> need.
Yeah, I figured you wouldn't like that part, especially based on your
discussion with Mark yesterday about the upcoming gendisk changes.
EVMS has traditionally used the gendisk list to get information about what
disks are available in the system. The walk_gendisk() function in genhd.c was
suggested last year by Christoph as a method for safely accessing the list,
and even made it into the 2.4 kernel. Thus we just ported it forward to 2.5
in our tree. It worked just fine in its original form until 2.5.40. Based on
your comments in genhd.c about the gendisks array, I assumed further changes
would be coming. But we had to come up with an interim solution to work on
2.5.40, and thus we have the version in the submitted patch, which I did not
intend to be a permanent solution.
So the question is, will there be a method to simply get a list of registered
disks on the system, or an API to call to run a function for each disk? If
so, we'll gladly switch to using that. If not, do you have any suggestions
for how this kind of functionality can be achieved with your upcoming changes?
--
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2002-10-02 22:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 21:33 EVMS Submission for 2.5 Kevin Corry
2002-10-02 22:14 ` Alexander Viro
2002-10-02 22:03 ` Kevin Corry [this message]
2002-10-02 23:02 ` Alexander Viro
2002-10-03 13:04 ` Kevin Corry
2002-10-03 14:51 ` Alexander Viro
2002-10-03 14:53 ` Kevin Corry
2002-10-03 15:37 ` Alexander Viro
2002-10-03 16:13 ` Greg KH
2002-10-03 16:21 ` Alexander Viro
2002-10-03 16:30 ` Greg KH
2002-10-03 17:00 ` David Lang
2002-10-03 17:27 ` Greg KH
2002-10-03 19:52 ` [Evms-devel] " Oliver Neukum
2002-10-03 21:37 ` Greg KH
2002-10-03 21:02 ` Oliver Neukum
2002-10-03 22:56 ` Greg KH
2002-10-03 23:03 ` Alexander Viro
2002-10-04 8:07 ` Oliver Neukum
2002-10-05 0:06 ` Greg KH
2002-10-03 16:55 ` Patrick Mochel
2002-10-03 19:24 ` Linus Torvalds
2002-10-02 22:27 ` Shawn
2002-10-02 22:19 ` Shawn
2002-10-02 22:43 ` Greg KH
2002-10-03 12:13 ` Kevin Corry
2002-10-03 16:23 ` Greg KH
2002-10-03 16:51 ` Linus Torvalds
2002-10-03 21:56 ` Kevin Corry
2002-10-03 23:07 ` Greg KH
2002-10-04 0:39 ` Kevin Corry
2002-10-04 13:06 ` Alan Cox
2002-10-04 13:07 ` [Evms-devel] " Kevin Corry
2002-10-04 17:29 ` Kai Henningsen
2002-10-03 14:32 ` Christoph Hellwig
2002-10-03 14:59 ` [Evms-devel] " Michael Clark
2002-10-03 15:08 ` Christoph Hellwig
2002-10-03 15:03 ` Shawn
2002-10-03 15:31 ` Christoph Hellwig
2002-10-03 15:41 ` [Evms-devel] " Mike Tran
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=02100217031903.18102@boiler \
--to=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox