[PATCH v4 00/20] NVMeTCP Offload ULP

[Hannes Reinecke]

On 7/7/21 5:07 PM, Keith Busch wrote:
> On Wed, Jul 07, 2021 at 04:58:44PM +0200, Hannes Reinecke wrote:
>> On 7/1/21 3:23 PM, Christoph Hellwig wrote:
>>> I looked over it a bit (and will send some individual comments), and I
>>> have to say I really dislike how this layer and how the hardware works.
>>>
>>> The whole point of NVMe is that we have a nicely standardized PCIe
>>> register level interface.  One that you can trivially hide a TCP offload
>>> under with just a little control plane logic.  But instead we come up with
>>> this gigant mess.
>>>
>> I can't really see how this control plane logic should work; how would the
>> entire NVMe-oF discovery be abstracted away to hide behind an NVMe-PCI
>> device?
> 
> Devices are already doing this. The discovery setup is device specific,
> though.
> 
Oh, grand.
I hoped we could steer away from this after the horrible experience we 
had with iSCSI offload engines.
I'd rather have a standardized way for this.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare at suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer