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?
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.)
...
> --- ./include/scsi/scsi_host.h 27 May 2006 15:58:17 -0000 1.27.2.1
> +++ ./include/scsi/scsi_host.h 19 May 2006 02:43:19 -0000 1.27
> @@ -541,6 +541,9 @@ struct Scsi_Host {
> */
> unsigned ordered_tag:1;
>
> + /* Are we currently performing an async scan? */
Perhaps add "private to scsi core" to the comment.
> + unsigned async_scan:1;
This flag is written under protection of async_scan_lock but read
without lock protection and without being an atomic variable. Is this
safe? I suppose it is as long as scan methods (by do_scan_async kthread,
by another thread associated to the LLDD or transport, by userspace) are
not mixed.
--
Stefan Richter
-=====-=-==- -=-= ===--
http://arcgraph.de/sr/
-
: 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
