Mike Christie <[email protected]> wrote: >>> If the device name and port do not change normally that seems better to >>> me since it works like the other drivers
just to be on the same page, when you say the other drivers (=transports) this doesn't include tcp, correct? for the tcp what's supported in the --net-- device name such that a BINDTODEVICE setsockopt is done to bind the socket to this netdevice. As for the IB device name and port number, indeed they don't change normally, but OTOH the rdma-cm api which iser is using is IP base and reolves IB local/remote addresses (= GUIDs which relate to devices/ports) from IP addresses/routing rules and not the other way around. I understand using IP is a bit problematic when DHCP is used for the initiator, let me think about that a bit, thanks 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.
