[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240719091959.17163-2-jacky_gam_2001@163.com>
Date: Fri, 19 Jul 2024 17:19:58 +0800
From: Ping Gan <jacky_gam_2001@....com>
To: hare@...e.de,
hch@....de,
sagi@...mberg.me,
kch@...dia.com,
linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org
Cc: ping.gan@...l.com,
Ping Gan <jacky_gam_2001@....com>
Subject: [PATCH v3 1/2] nvmet-tcp: use unbound_wq for nvmet-tcp by default
To use unbounded workqueue to handle TCP's IO by default, which
was discussed in below session.
https://lore.kernel.org/lkml/20240719084953.8050-1-jacky_gam_2001@163.com/
Signed-off-by: Ping Gan <jacky_gam_2001@....com>
---
drivers/nvme/target/tcp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c
index 5bff0d5464d1..35713472e395 100644
--- a/drivers/nvme/target/tcp.c
+++ b/drivers/nvme/target/tcp.c
@@ -2198,7 +2198,7 @@ static int __init nvmet_tcp_init(void)
int ret;
nvmet_tcp_wq = alloc_workqueue("nvmet_tcp_wq",
- WQ_MEM_RECLAIM | WQ_HIGHPRI, 0);
+ WQ_MEM_RECLAIM | WQ_HIGHPRI | WQ_UNBOUND | WQ_SYSFS, 0);
if (!nvmet_tcp_wq)
return -ENOMEM;
--
2.26.2
Powered by blists - more mailing lists