> The kernel is a large piece that keeps moving on - its made of many smaller > pieces/components, but with very sharp and well defined dependencies and > interactions. The rdma stack is far from being an isolated piece which you > can pull from kernel X and plug into kernel Y - this applies all over the > place in varying extents - e.g from the RDMA HW drivers, through the IB core > and up to the ULPs. > > The latter is the easiest to explain, as Roland once commented, each IB ULP > driver is a fish and a eel - so SRP/iSER/rNFS/IPoIB are all IB fishes > working with the IB core services and with the HW through the verbs, but the > are part from higher-level constructs in the kernel, such as being network > device (IPoIB), SCSI Low Level drivers (1st two), iscsi transport provider > (iser) and RPC provider (rNFS). Now, BACKPORTING these stacks (SCSI, iSCSI, > RPC/NFS, etc) isn't something that OFA can carry, and it would be > self-damaging to create notion with end-users that OFED does so. I tend to > think this is done now for rNFS, and its a mistake. Distributions do that, > by the way, but its part of their bread and butter.
https://lkml.org/lkml/2011/9/9/327 and its links have interesting and possibly useful information about the wireless-compat backporting project. In fact it might make sense to try and merge OFED efforts into that compat project. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
