From: scameron@beardog.cce.hp.com
To: Tejun Heo <tj@kernel.org>
Cc: axboe@kernel.dk, neilb@suse.de, hch@infradead.org,
jmoyer@redhat.com, hare@suse.de, shaohua.li@intel.com,
vgoyal@redhat.com, stephenmcameron@gmail.com,
linux-kernel@vger.kernel.org, lsorense@csclub.uwaterloo.ca,
scameron@beardog.cce.hp.com
Subject: Re: [RFC PATCH] block: Add new generic block device naming interface
Date: Thu, 25 Apr 2013 16:07:26 -0500 [thread overview]
Message-ID: <20130425210726.GL7917@beardog.cce.hp.com> (raw)
In-Reply-To: <20130425204033.GB10990@mtj.dyndns.org>
On Thu, Apr 25, 2013 at 01:40:33PM -0700, Tejun Heo wrote:
> Hello,
>
> On Thu, Apr 25, 2013 at 03:22:15PM -0500, Stephen M. Cameron wrote:
> > If block drivers could (optionally) share a common device namespace then
> > grub could be taught about this common namespace once, and any new block
> > device drivers could take advantage of this namespace and grub would
> > automatically work with them.
>
> Hmmm... maybe I'm missing something but the names assigned this way
> wouldn't have any kind of stability across boots. Is that good
> enough?
Perhaps not. I am open to suggestions on that front -- perhaps there's
some way for udev to help sort things out?
> But, if so, I'm kinda having hard time understanding what
> it'd be able to do which any other name can't do.
>
> Can you please elaborate the use case?
Sure.
Right now, if you add a new block driver, if you want grub to be able
to boot it, you also have to modify grub. This is true for each new
block driver that comes along. This is not the case for SCSI HBA
drivers, because they all get to share the sd driver and its device
name space, and grub already knows about that. You can add all kinds
of SCSI HBA drivers and never have to worry about needing to modify
grub to get boot support.
It seems wrong to me that for every new block driver needing boot support
grub has to be modified. If there were a common block device name space
which grub knew about, any new block driver which comes along that needs
support from grub could get it by using this common block device name space.
So that is the problem I'd like to solve. I realize the patch I've put
up for discussion may fall short. And it's possible there's a good reason
such a thing as I propose isn't already present, in which case I'd like
to learn what that reason is.
Thanks,
-- steve
next prev parent reply other threads:[~2013-04-25 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 20:22 [RFC PATCH] block: Add new generic block device naming interface Stephen M. Cameron
2013-04-25 20:40 ` Tejun Heo
2013-04-25 21:07 ` scameron [this message]
2013-04-25 21:14 ` Tejun Heo
2013-04-25 22:12 ` scameron
2013-04-26 19:03 ` Tejun Heo
2013-04-29 14:56 ` Hannes Reinecke
2013-04-29 15:17 ` Vivek Goyal
2013-04-29 16:06 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2013-03-28 16:18 Stephen M. Cameron
2013-03-11 19:00 Stephen M. Cameron
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=20130425210726.GL7917@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=neilb@suse.de \
--cc=shaohua.li@intel.com \
--cc=stephenmcameron@gmail.com \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
/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.