[PATCH 0/7] RFC patch series - NVMeTCP Offload ULP

[Max Gurtovoy]

On 11/19/2020 4:21 PM, Shai Malin wrote:
> This patch series introduces the nvme-tcp-offload ULP host layer, which will be a new transport type called "tcp-offload" and will serve as an abstraction layer to work with vendor specific nvme-tcp offload drivers.
>
> The nvme-tcp-offload transport can co-exist with the existing tcp and other transports. The tcp offload was designed so that stack changes are kept to a bare minimum: only registering new transports. All other APIs, ops etc. are identical to the regular tcp transport.
> Representing the TCP offload as a new transport allows clear and manageable differentiation between the connections which should use the offload path and those that are not offloaded (even on the same device).

why can't we extend the current NVMe-TCP driver and register vendor ops 
to it, instead of duplicating the entire driver ?

AFAIU, only the IO path logic is vendor specific but all the rest is the 
same.