10eb0f013c
When we create the tcp/ip connection by calling ep_connect, we currently just go by the routing table info. I think there are two problems with this. 1. Some drivers do not have access to a routing table. Some drivers like qla4xxx do not even know about other ports. 2. If you have two initiator ports on the same subnet, the user may have set things up so that session1 was supposed to be run through port1. and session2 was supposed to be run through port2. It looks like we could end with both sessions going through one of the ports. Fixes for cxgb3i from Karen Xie. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> |
||
|---|---|---|
| .. | ||
| cxgb3i_ddp.c | ||
| cxgb3i_ddp.h | ||
| cxgb3i_init.c | ||
| cxgb3i_iscsi.c | ||
| cxgb3i_offload.c | ||
| cxgb3i_offload.h | ||
| cxgb3i_pdu.c | ||
| cxgb3i_pdu.h | ||
| cxgb3i.h | ||
| Kbuild | ||
| Kconfig | ||