[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69f9a7c3-e2ab-454a-2713-2e9c9dea4e47@grimberg.me>
Date: Wed, 13 Jan 2021 17:27:17 -0800
From: Sagi Grimberg <sagi@...mberg.me>
To: Boris Pismenny <borisp@...lanox.com>, kuba@...nel.org,
davem@...emloft.net, saeedm@...dia.com, hch@....de, axboe@...com,
kbusch@...nel.org, viro@...iv.linux.org.uk, edumazet@...gle.com
Cc: yorayz@...dia.com, boris.pismenny@...il.com, benishay@...dia.com,
linux-nvme@...ts.infradead.org, netdev@...r.kernel.org,
ogerlitz@...dia.com
Subject: Re: [PATCH v1 net-next 00/15] nvme-tcp receive offloads
Hey Boris, sorry for some delays on my end...
I saw some long discussions on this set with David, what is
the status here?
I'll take some more look into the patches, but if you
addressed the feedback from the last iteration I don't
expect major issues with this patch set (at least from
nvme-tcp side).
> Changes since RFC v1:
> =========================================
> * Split mlx5 driver patches to several commits
> * Fix nvme-tcp handling of recovery flows. In particular, move queue offlaod
> init/teardown to the start/stop functions.
I'm assuming that you tested controller resets and network hiccups
during traffic right?
Powered by blists - more mailing lists