[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <253cydizv99.fsf@nvidia.com>
Date: Fri, 11 Apr 2025 16:24:18 +0300
From: Aurelien Aptel <aaptel@...dia.com>
To: Christoph Hellwig <hch@....de>, sagi@...mberg.me
Cc: Simon Horman <horms@...nel.org>, kuba@...nel.org,
linux-nvme@...ts.infradead.org, netdev@...r.kernel.org, sagi@...mberg.me,
hch@....de, kbusch@...nel.org, axboe@...com, chaitanyak@...dia.com,
davem@...emloft.net, aurelien.aptel@...il.com, smalin@...dia.com,
malin1024@...il.com, ogerlitz@...dia.com, yorayz@...dia.com,
borisp@...dia.com, galshalom@...dia.com, mgurtovoy@...dia.com,
tariqt@...dia.com
Subject: Re: [PATCH v27 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer
registration
Christoph Hellwig <hch@....de> writes:
> Btw, just as a reminder nvme code has to go through the nvme tree, and
> there is absolutely no consesnsus on this feature yet.
Sagi, could you give your input on this?
Thanks
Powered by blists - more mailing lists