--- James Bottomley <James.Bottomley@xxxxxxxxxxxx> wrote:
> As you can see, for a driver that provides an SMP tap, like aic94xx then
Please don't call it a "tap". Use storage terminology please.
> these parameters can be got by the transport class sending the SMP
> queries ... the driver doesn't need to know about it.
Exactly what the SAS stack does.
Furthermore you need to understand that this is _not_ anything special.
I've explained that before: aic94xx only provides access to SDS, and
then the SAS stack uses that. That is, the "scsi_host" abstraction is
at the SAS stack layer, not at "aic94xx".
This is the provision which "sas_ha->lldd_execute_task" wants and
which aic94xx provides. It could be any task supported by the SDS.
See "struct sas_task" in include/scsi/sas/sas_task.h.
So, you can safely presume that any transport would support executing
a SCSI task, which is the abstraction at SCSI Core level. But
at the transport (lower) level, "struct sas_task" supports SCSI task
as well as transport specific tasks.
Luben
-
: 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
