> On the other hand trying to hook offloaded iWARP into the normal stack > does seem to lead to a mess. I see DaveM's point: TCP port space is > just the beginning -- filtering, queueing, etc also have config that > ultimately an offload device would want to hook too.
TCP port space is just the beginning but then these features didn't show up all at once in the kernel either. Instead of evolving iWARP implementation, we can't even take a baby step and fix a flaw that exists in the current kernel. Why are we "replicating" everything offered by the host stack instead of hooking in? It does not sound like good engineering to me. Chien -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
