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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/