On 01/04/2012 01:22 PM, Or Gerlitz wrote: > Eddie Wai <[email protected]> wrote: >> Yes, I think it would be beneficial to add the passing of the iface_num >> parameter to the transport's ep_connect call so that it can identify >> which iface profile to use. This should help HW transports that have >> support for more than one iface profile. For bnx2i in particular, this >> iface_num >> Handle will then get passed to iscsiuio for iface identification. > > What about non HW transports such as iser which has its ep_connect in > the kernel, can we also get exposure to that ifcase profile, if yes, > how? and if not, what needs to be done for this to happen?
Not like what Eddie is describing. iscsiuio is another userspace daemon that does some hw offload iscsi stuff like dhcp. 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? -- 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.
