On 09/17/2010 02:03 PM, Joe Eykholt wrote:
How about instead of adding use_serial_number, let's just have the
drivers that want a serial number call scsi_cmd_get_serial()
I think this sounds better.
You could also convert drivers to the host tagging if you needed a
unique id for each command sent to a host.
and stop calling it from scsi_dispatch_cmd()? AFAICT, it's only
used in debug messages in some drivers. I didn't find other usages
but didn't do an exhaustive search.
The comments for serial_number say that it is only supposed to be used
for debugging printks and most drivers use it for that. However, it
looks like mpt and dpt_i2o are using it for error handling and/or lookup
type of operations. I think the mpt* uses are not needed in the abort
checks.
And eata is using it for ordering and tracking or something. It could
probably be converted to the host tagging if or what you suggested if it
needs the uniqueue id.
zfcp looks like it copies it. It does not look like the driver needs it.
scsi_error.c uses it in scsi_try_to_abort_cmd to check if a command has
completed, but I think that can be done by checking if REQ_ATOM_COMPLETE
is set.
--
To unsubscribe from this list: 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
