Re: [PATCH v12 10/26] nvme-tcp: Deal with netdevice DOWN events
From: Sagi Grimberg <sagi@grimberg.me>
Date: 2023-08-09 08:00:31
Also in:
linux-nvme
On 7/12/23 19:14, Aurelien Aptel wrote:
quoted hunk ↗ jump to hunk
From: Or Gerlitz <redacted> 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 destroys them. Use netdevice notifier for that matter -- offloaded connections are stopped before the stack continues to call the NIC driver close ndo. We use the existing recovery flow which has the advantage of resuming the offload once the connection is re-set. This also buys us proper handling for the UNREGISTER event b/c our offloading starts in the UP state, and down is always there between up to unregister. Signed-off-by: Or Gerlitz <redacted> Signed-off-by: Boris Pismenny <borisp@nvidia.com> Signed-off-by: Ben Ben-Ishay <redacted> Signed-off-by: Yoray Zack <redacted> Signed-off-by: Shai Malin <redacted> Signed-off-by: Aurelien Aptel <redacted> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> --- drivers/nvme/host/tcp.c | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+)diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c index df58668cbad6..e68e5da3df76 100644 --- a/drivers/nvme/host/tcp.c +++ b/drivers/nvme/host/tcp.c@@ -221,6 +221,7 @@ struct nvme_tcp_ctrl { static LIST_HEAD(nvme_tcp_ctrl_list); static DEFINE_MUTEX(nvme_tcp_ctrl_mutex); +static struct notifier_block nvme_tcp_netdevice_nb; static struct workqueue_struct *nvme_tcp_wq; static const struct blk_mq_ops nvme_tcp_mq_ops; static const struct blk_mq_ops nvme_tcp_admin_mq_ops;@@ -3234,6 +3235,30 @@ static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev, return ERR_PTR(ret); } +static int nvme_tcp_netdev_event(struct notifier_block *this, + unsigned long event, void *ptr) +{ + struct net_device *ndev = netdev_notifier_info_to_dev(ptr); + struct nvme_tcp_ctrl *ctrl; + + switch (event) { + case NETDEV_GOING_DOWN: + mutex_lock(&nvme_tcp_ctrl_mutex); + list_for_each_entry(ctrl, &nvme_tcp_ctrl_list, list) { + if (ndev == ctrl->offloading_netdev) + nvme_tcp_error_recovery(&ctrl->ctrl); + } + mutex_unlock(&nvme_tcp_ctrl_mutex); + flush_workqueue(nvme_reset_wq);
In what context is this called? because every time we flush a workqueue, lockdep finds another reason to complain about something... Otherwise looks good, Reviewed-by: Sagi Grimberg <sagi@grimberg.me>