[PATCHv2] nvme-tcp: Implement recvmsg() receive flow

[Sagi Grimberg]

>> I did not expect anyone to fiddle with RFS for softirq context. The main
>> benefit of softirq context RX (outside of latency reduction) is that it
>> makes io_work handle ONLY TX, which is probably somewhat more efficient.
>
> But we still could do that, right?
> We can easily split the current io_work() into two parts, the TX part 
> driven from queue_rq(), and the RX part driven from the data_ready()
> callback, no?

We could, but then we create yet another kthread context. The main thing 
that makes this appealing is running RX from soft-irq.