From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCHES] add ata scsi driver
Date: Tue, 27 May 2003 12:16:24 -0400 [thread overview]
Message-ID: <20030527161624.GC21744@gtf.org> (raw)
In-Reply-To: <1054051233.1975.139.camel@mulgrave>
On Tue, May 27, 2003 at 12:00:28PM -0400, James Bottomley wrote:
> On Tue, 2003-05-27 at 11:50, Jeff Garzik wrote:
> > Oh, no question. My main interest is having a persistent id for a
> > device's media. Then Linux can use that to allow mapping in case device
> > names or majors change at each boot (and similar situations).
>
> Well, OK, that's not an in-kernel issue.
It's definitely an in-kernel issue, because the mapping is in-kernel now:
<major,minor> -> queue
> My current thought for this is that deriving the unique name can be
> awfully device specific (even in SCSI there are several fallback methods
> plus the usual black/white list of things that don't quite return
> entirely unique objects).
Agreed. And kernel assistance is likely necessary in many cases to
obtain the unique id, even if it's only userspace that's reading it.
> Thus, I think the derivation probably belongs
> in userspace as part of hotplug. Once the unique ID is determined, it
> could be written to a well known place in the sysfs tree for all the
> rest of the OS (things like udev for persistent device naming) to use.
Agreed, with the above proviso.
Jeff
next prev parent reply other threads:[~2003-05-27 16:03 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 18:12 [BK PATCHES] add ata scsi driver James Bottomley
2003-05-26 18:18 ` Jens Axboe
2003-05-26 18:47 ` James Bottomley
2003-05-26 19:07 ` Jens Axboe
2003-05-26 19:17 ` James Bottomley
2003-05-26 19:33 ` Jens Axboe
2003-05-27 12:39 ` Jens Axboe
2003-05-27 14:26 ` James Bottomley
2003-05-27 17:16 ` Jens Axboe
2003-05-27 18:09 ` James Bottomley
2003-05-27 18:21 ` Jens Axboe
2003-05-27 18:30 ` James Bottomley
2003-05-26 20:27 ` Linus Torvalds
2003-05-26 20:36 ` James Bottomley
2003-05-26 20:45 ` Linus Torvalds
2003-05-26 20:51 ` Jens Axboe
2003-05-26 20:56 ` James Bottomley
2003-05-26 20:38 ` Jens Axboe
2003-05-26 20:49 ` Linus Torvalds
2003-05-26 20:57 ` Jens Axboe
2003-05-26 21:34 ` Linus Torvalds
2003-05-26 23:58 ` Nick Piggin
2003-05-27 0:09 ` Linus Torvalds
2003-05-27 0:49 ` Nick Piggin
2003-05-27 0:16 ` Alan Cox
2003-05-27 6:54 ` Jens Axboe
2003-05-27 14:20 ` James Bottomley
2003-05-27 14:36 ` Linus Torvalds
2003-05-27 14:59 ` James Bottomley
2003-05-27 15:21 ` Jeff Garzik
2003-05-27 15:38 ` James Bottomley
2003-05-27 15:50 ` Jeff Garzik
2003-05-27 16:00 ` James Bottomley
2003-05-27 16:16 ` Jeff Garzik [this message]
2003-05-28 9:35 ` Christoph Hellwig
2003-05-28 10:50 ` Lincoln Dale
2003-05-27 19:43 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 4:58 Jeff Garzik
2003-05-26 5:15 ` Linus Torvalds
2003-05-26 5:30 ` Jeff Garzik
2003-05-26 5:36 ` Jeff Garzik
2003-05-26 5:42 ` Linus Torvalds
2003-05-26 6:01 ` Jeff Garzik
2003-05-26 16:56 ` Linus Torvalds
2003-05-26 17:47 ` Jeff Garzik
2003-05-26 20:09 ` Linus Torvalds
2003-05-27 0:29 ` Alan Cox
2003-05-27 6:07 ` Jeff Garzik
2003-05-27 6:30 ` Linus Torvalds
2003-05-27 6:51 ` Linus Torvalds
2003-05-27 7:29 ` Jeff Garzik
2003-05-26 5:40 ` Linus Torvalds
2003-05-26 5:53 ` Jeff Garzik
2003-05-26 6:21 ` Jeff Garzik
2003-05-26 16:57 ` Linus Torvalds
2003-05-26 17:24 ` Jens Axboe
2003-05-26 17:54 ` Jeff Garzik
2003-05-26 17:59 ` Jeff Garzik
2003-05-26 18:11 ` Jens Axboe
2003-05-27 0:22 ` Alan Cox
2003-05-27 4:15 ` Linus Torvalds
2003-05-26 10:32 ` Bartlomiej Zolnierkiewicz
2003-05-26 11:13 ` Jeff Garzik
2003-05-26 11:37 ` Bartlomiej Zolnierkiewicz
2003-05-26 5:59 ` Benjamin Herrenschmidt
2003-05-26 6:03 ` Jeff Garzik
2003-06-02 9:46 ` Andre Hedrick
2003-06-02 13:56 ` Alan Cox
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=20030527161624.GC21744@gtf.org \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.