Hi Mike,

I am still looking over/understanding the patches but could I trouble
you patch this against the uIP offload tree?  

Thanks again.


On Sun, 2009-08-30 at 14:31 -0700, Mike Christie wrote:
> For offlaod cards, bnx2i, cxgb3i and be2iscsi, we have to do discovery 
> through a second network interface. The two attached patches has us 
> instead do discovery through the iscsi class interface, so you do not 
> have to set up a seperate nic for discovery and you do not have to worry 
> about IP based ACLS on the target.
> The 0001-iscsiadm-use-kernel-pdu-passthrough-for-sendtargets.patch patch 
> was made over the open-iscsi git tree. It is only userspce code.
> The 0001-libiscsi-fix-login-text-checks-in-pdu-injection-cod.patch patch 
> is made over linux-2.6-iscsi's iscsi branch. It should probably apply to 
> other kernels though.
> Please give the patches a try.
> Here are some known limits:
> MaxRecvSegmentLength is hard coded to 8K for discovery sessions, because 
> the kernel conn->data buffer and driver related buffers were hard coded 
> to this value and some netlink's buffers are too.
> I have only tested cxgb3i.
> Ben, this is not patched against the uip offload tree but I can do that 
> for you.
> Michael and Anil, I was not sure where to handle text response pdus in 
> bnx2i_process_new_cqes? I am currently sending the discovery session 
> login and text pdus through the same interface you get nops or normal 
> session login pdus, so I think bnx2i_mtask_xmit should just work (I 
> limited MaxRecvSegmentLength to ISCSI_DEF_MAX_RECV_SEG_LEN, so the buf 
> sizes are ok.).
> Jay, not sure how text response pdus are coming in? Are they like login 
> or logout pdus?

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