[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <967ae867-42c9-731d-9cb1-2c81fcc1ef77@gmail.com>
Date: Wed, 13 Jan 2021 21:47:40 -0700
From: David Ahern <dsahern@...il.com>
To: Sagi Grimberg <sagi@...mberg.me>,
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
On 1/13/21 6:27 PM, Sagi Grimberg wrote:
>> 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?
I had questions on this part as well -- e.g., what happens on a TCP
retry? packets arrive, sgl filled for the command id, but packet is
dropped in the stack (e.g., enqueue backlog is filled, so packet gets
dropped)
Powered by blists - more mailing lists