Re: [PATCH net-next RFC v1 08/10] nvme-tcp: Deal with netdevice DOWN events

2020-10-10 Thread Or Gerlitz
On Fri, Oct 9, 2020 at 1:50 AM Sagi Grimberg wrote: > > @@ -412,8 +413,6 @@ int nvme_tcp_offload_limits(struct nvme_tcp_queue > > *queue, > > queue->ctrl->ctrl.max_segments = limits->max_ddp_sgl_len; > > queue->ctrl->ctrl.max_hw_sectors = > > lim

Re: [PATCH net-next RFC v1 08/10] nvme-tcp: Deal with netdevice DOWN events

2020-10-08 Thread Sagi Grimberg
On 9/30/20 9:20 AM, Boris Pismenny wrote: From: Or Gerlitz For ddp setup/teardown and resync, the offloading logic uses HW resources at the NIC driver such as SQ and CQ. These resources are destroyed when the netdevice does down and hence we must stop using them before the NIC driver destro

[PATCH net-next RFC v1 08/10] nvme-tcp: Deal with netdevice DOWN events

2020-09-30 Thread Boris Pismenny
From: Or Gerlitz For ddp setup/teardown and resync, the offloading logic uses HW resources at the NIC driver such as SQ and CQ. These resources are destroyed when the netdevice does down and hence we must stop using them before the NIC driver destroyes them. Use netdevice notifier for that matt