From: Aurelien Aptel <aaptel@nvidia.com>
To: linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
sagi@grimberg.me, hch@lst.de, kbusch@kernel.org, axboe@fb.com,
chaitanyak@nvidia.com, davem@davemloft.net, kuba@kernel.org
Cc: Or Gerlitz <ogerlitz@nvidia.com>,
aaptel@nvidia.com, aurelien.aptel@gmail.com, smalin@nvidia.com,
malin1024@gmail.com, yorayz@nvidia.com, borisp@nvidia.com,
galshalom@nvidia.com, mgurtovoy@nvidia.com
Subject: [PATCH v13 10/24] nvme-tcp: Deal with netdevice DOWN events
Date: Tue, 22 Aug 2023 15:04:11 +0000 [thread overview]
Message-ID: <20230822150425.3390-11-aaptel@nvidia.com> (raw)
In-Reply-To: <20230822150425.3390-1-aaptel@nvidia.com>
From: Or Gerlitz <ogerlitz@nvidia.com>
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 <ogerlitz@nvidia.com>
Signed-off-by: Boris Pismenny <borisp@nvidia.com>
Signed-off-by: Ben Ben-Ishay <benishay@nvidia.com>
Signed-off-by: Yoray Zack <yorayz@nvidia.com>
Signed-off-by: Shai Malin <smalin@nvidia.com>
Signed-off-by: Aurelien Aptel <aaptel@nvidia.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
---
drivers/nvme/host/tcp.c | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 9253cc826571..b187cd36e016 100644
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -234,6 +234,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;
@@ -3155,6 +3156,32 @@ 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)
+{
+#ifdef CONFIG_ULP_DDP
+ 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->ddp_netdev)
+ nvme_tcp_error_recovery(&ctrl->ctrl);
+ }
+ mutex_unlock(&nvme_tcp_ctrl_mutex);
+ flush_workqueue(nvme_reset_wq);
+ /*
+ * The associated controllers teardown has completed,
+ * ddp contexts were also torn down so we should be
+ * safe to continue...
+ */
+ }
+#endif
+ return NOTIFY_DONE;
+}
+
static struct nvmf_transport_ops nvme_tcp_transport = {
.name = "tcp",
.module = THIS_MODULE,
@@ -3170,6 +3197,8 @@ static struct nvmf_transport_ops nvme_tcp_transport = {
static int __init nvme_tcp_init_module(void)
{
+ int ret;
+
BUILD_BUG_ON(sizeof(struct nvme_tcp_hdr) != 8);
BUILD_BUG_ON(sizeof(struct nvme_tcp_cmd_pdu) != 72);
BUILD_BUG_ON(sizeof(struct nvme_tcp_data_pdu) != 24);
@@ -3184,8 +3213,19 @@ static int __init nvme_tcp_init_module(void)
if (!nvme_tcp_wq)
return -ENOMEM;
+ nvme_tcp_netdevice_nb.notifier_call = nvme_tcp_netdev_event;
+ ret = register_netdevice_notifier(&nvme_tcp_netdevice_nb);
+ if (ret) {
+ pr_err("failed to register netdev notifier\n");
+ goto out_free_workqueue;
+ }
+
nvmf_register_transport(&nvme_tcp_transport);
return 0;
+
+out_free_workqueue:
+ destroy_workqueue(nvme_tcp_wq);
+ return ret;
}
static void __exit nvme_tcp_cleanup_module(void)
@@ -3193,6 +3233,7 @@ static void __exit nvme_tcp_cleanup_module(void)
struct nvme_tcp_ctrl *ctrl;
nvmf_unregister_transport(&nvme_tcp_transport);
+ unregister_netdevice_notifier(&nvme_tcp_netdevice_nb);
mutex_lock(&nvme_tcp_ctrl_mutex);
list_for_each_entry(ctrl, &nvme_tcp_ctrl_list, list)
--
2.34.1
next prev parent reply other threads:[~2023-08-22 15:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 15:04 [PATCH v13 00/24] nvme-tcp receive offloads Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 01/24] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 02/24] net/ethtool: add new stringset ETH_SS_ULP_DDP_{CAPS,STATS} Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 03/24] net/ethtool: add ULP_DDP_{GET,SET} operations for caps and stats Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 04/24] Documentation: document netlink ULP_DDP_GET/SET messages Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 05/24] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 06/24] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 07/24] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 08/24] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 09/24] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-08-22 15:04 ` Aurelien Aptel [this message]
2023-08-22 15:04 ` [PATCH v13 11/24] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 12/24] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 13/24] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 14/24] net/mlx5e: Have mdev pointer directly on the icosq structure Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 15/24] net/mlx5e: Refactor doorbell function to allow avoiding a completion Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 16/24] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 17/24] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 18/24] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 19/24] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 20/24] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 21/24] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 22/24] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 23/24] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 24/24] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2023-08-24 2:02 ` [PATCH v13 00/24] nvme-tcp receive offloads Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230822150425.3390-11-aaptel@nvidia.com \
--to=aaptel@nvidia.com \
--cc=aurelien.aptel@gmail.com \
--cc=axboe@fb.com \
--cc=borisp@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=davem@davemloft.net \
--cc=galshalom@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mgurtovoy@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@nvidia.com \
--cc=sagi@grimberg.me \
--cc=smalin@nvidia.com \
--cc=yorayz@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox