On 03/01/2010 02:46 AM, Or Gerlitz wrote:
Mike Christie wrote:
Ah never mind. For some reason I thought you had to have a mask, but if
you give rdma_resolve_addr a addr then it will do the right thing and
use only the port you wanted right?
YES. providing rdma_resolve_addr a source address is like calling rdma_bind
with this source address and then calling rdma_resolve_address with only
destination address. So its like bind(2) in that respect. Currently the rdma
stack through the include/rdma/rdma_cm.h rdma-cm api doesn't support things
like SO_BINDTODEVICE to either of network or rdma device. But even if it
would/will, I prefer to stay with IP addresses.
I am not sure I got why you prefer to use the IP? Was your reason that
part you wrote about iser being IP based?
I understand how SO_BINDTODEVICE is used for the tcp transport, but its all done
in user space, and later when the connection is bounded to the end-point (<--
socket created/binded/connected from user space) things are moved to the kernel.
This isn't the case with iser. I believe that at this point we agree that there
should be a way to specify the source address bounded by the user to the iscsi
interface to the kernel iser transport code, correct?
Whether it is done in the kernel or userspace or if you support
SO_BINDTODEVICE or not is not a issue. We can change userspace so you
get a device like tcp and offload and/or we can change the kernel in any
sane way so you can bind by whatever. You do not have to support
SO_BINDTODEVICE. You can work like how the offload drivers do.
I am not sure where you get that I agree ip address is best. All I am
saying above is I think I see the API you wanted to use.
If the device name and port do not change normally that seems better to
me since it works like the other drivers.
--
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.
