> >> The sysfs bits related to the hba should be use one of the scsi sysfs > >> facilities or if they are related to iscsi bits and are generic then > >> through the iscsi hba > > > > bnx2i needs 2 sysfs entries - > > 1. QP size info - this is used to size per connection shared data > > structures to issue work requests to chip (login, scsi cmd, tmf, nopin) > > and get completions from the chip (scsi completions, async messages, > > etc'). This is a iSCSI HBA attribute > > 2. port mapper - we can be more flexible on classifying this as either > > iSCSI HBA attribute or bnx2i driver global attribute > > Can hooks be added to iSCSI transport class to include these? > > > > Which ones were they exactly? I think JamesB wanted only common > transport values in the transport class. If it is driver specific then > it should go on the host or target or device with the scsi_host_template > attrs. >
It's a chicken & egg issue to put "port mapper" sysfs entry in scsi host attributes. Application won't see sysfs unless initiator creates an iSCSI session and driver can't create an iSCSI session without a tcp port. I was wondering if there is a better way than using IOCTL in this situation? - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
