On Mon, 2006-05-29 at 07:05 -0600, Matthew Wilcox wrote: > On Mon, May 29, 2006 at 10:38:13AM +0200, Stefan Richter wrote: > > Matthew Wilcox wrote: > > > Add the scsi_mod.scan kernel parameter to determine how scsi busses > > > are scanned. "sync" is the current behaviour. "none" punts scanning > > > scsi busses to userspace. "async" is the new default. > > > > This parameter is only relevant with LLDDs which use scsi_scan_host, right? > > Not entirely. If you set it to "none", scsi_scan_target() also returns > without doing anything. If you use the scsi_prep_async_scan() and > scsi_finish_async_scan() API, you can also use this infrastructure to > make scanning sbp2 synchronised with other scsi hosts. Then the setting > of sync vs async also triggers old vs new behaviour. > > > Furthermore, "sync|async" basically means "serialized|parallelized > > across host adapters". Does it also mean "finishing before|after driver > > initialization"? (With LLDDs which use scsi_scan_host.) > > That's what scsi_complete_async_scans() is for. If you have a built-in > module, it will wait for the async scans to finish before we get as far > as trying to mount root. that sounds the wrong place, at least, I would expect the wait is needed before starting the initramfs, since that is where some distros mount their root (mount-by-label and I suspect many other cases will do it from there, such as iscsi rootfs etc) - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
