On Mon, Feb 26, 2007 at 10:10:15AM -0800, Eric Schrock wrote:
> On Mon, Feb 26, 2007 at 12:06:14PM -0600, Nicolas Williams wrote:
> > Couldn't all that tasting be done in parallel?
>
> Yep, that's certainly possible. Sounds like a perfect feature for
> someone in the community to work on :-) Simply take
> zpool_find_import(), add some worker thread/pool model, and there you
> go.
What is slow, BTW? The open(2)s of the devices? Or the label reading?
And is there a way to do async open(2)s w/o a thread per-open? The
open(2) man page isn't very detailed about O_NONBLOCK/O_NDELAY behaviour
on devices ("[s]ubsequent behaviour of the device is device-specific")...
Also, I see this happens in user-land. Is there any benefit of trying
this in kernel-land?
OT: I've been trying to get ZFS boot on a USB flash device going, and
currently that's failing to find the pool named in /etc/system -- next
time I try it I will check if this is something to do with USB modules
not loading or not in the minitroot (I don't have that USB stick with me
atm) or if zpool.cache refers to the wrong device or doesn't match
/devices. If ZFS boot could live without a zpool.cache to find the
volum with the boot root FS that would rock. Incidentally, it'd be nice
if I could more easily observe what is going wrong here with kmdb --
there must be a way to get more info from the ZFS module that I'm just
missing.
Nico
--
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
