James Smart wrote:
James,
What Krishna describes, is a need to add driver-specific attributes (and
optionally a directory of attributes) to a class-level object. I
attempted patches of a similar form when I was originally doing the
fc_rports, which were rejected.
I believe the position is that we do not allow driver-specific things on
the class objects, and drivers are limited in scope to only adding
individual attributes to the scsi_host via the attribute list in the
scsi_host_template.
I'd like to re-propose the patches to add driver-specific data to the FC
class objects. Do you believe there's a change in heart to accepting
this functionality before I start the work to create them ?
For example, I know that Emulex would have liked to add driver-specific
state data to the rports. And Krishna's proposal is another request.
We are having the same problem for iscsi. For qla4xxx and cxgb3i and
bnx2i, we would like to add driver specific attrs to the iscsi
session/connection which are like FC's rport struct.
I was hoping if at least the classes provide an API to add driver
specific attrs similar to how scsi-ml does, then it would be ok?
--
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
