On 07/18/2018 06:04 PM, Mike Christie wrote:
> On 07/18/2018 05:41 PM, Bart Van Assche wrote:
>> On Sun, 2018-07-15 at 18:16 -0500, Mike Christie wrote:
>>> Export the initiator port info in configfs
>>
>> Does configfs support soft links? Can this information be exported as a
>> soft link from the session directory to the struct se_portal_group configfs
>> object?
>>
>
> If you just needed to export the initiator name or if a single session
> per initiator can be connected to a tpg then it would work ok.
>
> The problem is for iscsi the scsi initiator port / transport id, is the
> initiator name and isid. The isid is just a 48 bit number and the
> initiator will allocate a new value for every session. So on the
> initiator side if there are multiple nics, then it is common to create a
> session through nic and each session will have the same initiator name
> but different isids. So at some place you need to put multiple files to
> export the different isids or indicate to userspace tools that there is
> more than one session connected to that tpg.
>
Oh wait, I think I know what you mean. Did you want something like this
where the symlink name is the info in the initiator_port file like this:
[tpgt_1]# tree -L 2
.
`-- sessions
`-- 1
| `-- iqn.2005-03.com.ceph:ini1,i,0x00023d000001 -> ../../tpgt_1
`--2
. `-- iqn.2005-03.com.ceph:ini1,i,0x00023d000002 -> ../../tpgt_1
If that is what you are asking about, I did not get why we want to link
to the tpg object, because we already know the tpg since it is the
parent of the session dir.
