On 06/18/2009 10:56 AM, Joachim Worringen wrote:
> Greetings,
> I tried to use Open-iSCSI with a non-tcp socket type and failed
> (timeout after connection has been established).
> Looking at the source, the reason is obvious: for sending data
> (iscsi_send()), the function pointers from sock->sk are used via the
> kernel socket API. This works well with non-tcp sockets. Howver, for
> reading data (see callback handler iscsi_tcp_data_ready()),
> tcp_read_sock() is used instead of the related kernel socket API call.

Sounds good. Could you test out your solution and send a patch?
If it tests out, I don't see why not.

> Is there a specific reason for this? iSCSI would surely benefit from
> using high-performance, non-tcp sockets if available (I'm talking
> about SuperSockets in this case, see 
> http://www.dolphinics.com/products/dolphin-supersockets.html).

Sure sounds nice. If it is a simple and compatible change it sounds very good.

>  thanks, Joachim


You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at http://groups.google.com/group/open-iscsi

Reply via email to