> For iser we will just have to pass what you need into the kernel. Do you > know exactly what you need passed down in the kernel driver already by any > chance?
So I wrote in the original post "quick examples are the source ip address for multi-pathing (e.g when done on 2 paths who use the same IP subnet), the maximal number of SCSI commands to be used for that session, vlan proirity for the case of this session being on IBoE environment and this IP subnet being served by 8021q vlan nic, etc. For the most case, these attributes are present in the iface structure" - the most important of these is the source IP set by the admin to the iscsi interface over which the login is done - for multi-pathing env. As I wrote, I saw that this param and other friends we can use are present on the iface profile structure and I wondered if this struct is available in the kernel for not HW transports. If not, and we want a dedicated netlink call ep_connect_ext - then lets add there the source IP, Ethernet 8021q Vlan priority bits and the max # of scsi commands for the session. If you come up with patch I'd love to test that... Or. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
