On Tue, 2006-12-05 at 11:45 +0100, Brice Goglin wrote: > Steve Wise wrote: > > There is no SW TCP stack in this driver. The HW supports RDMA over > > TCP/IP/10GbE in HW and this is required for zero-copy RDMA over Ethernet > > (aka iWARP). The device is a 10 GbE device, not Infiniband. > > Then, I wonder why the driver goes in drivers/infiniband/ :)
drivers/infiniband support both IB and IWARP transports. > Is there really no way to only keep the actual hw infiniband there, move > iwarp/rdma drivers in drivers/net/something/ and the core stuff in > net/something/ ? > Sure, this _could_ be done, but what I think you're missing is that applications use the interface exported by drivers/infiniband over both IB -and- IWARP transports. The application can be written to not care which transport is used. Examples of apps that can run over both transports using the same common interface: user mode: MVAPICH2, OMPI, IMPI, HPMPI, kernel mode: NFS-RDMA, iSER. Note that the include directory used by drivers/infiniband is now include/rdma. Perhaps drivers/infiniband should be renamed to drivers/rdma as well at some point... Steve. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
