From: Ping Gan <jacky_gam_2001@163.com>
To: hare@suse.de, hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: ping.gan@dell.com, Ping Gan <jacky_gam_2001@163.com>
Subject: [PATCH v3 1/2] nvmet-tcp: use unbound_wq for nvmet-tcp by default
Date: Fri, 19 Jul 2024 17:19:58 +0800 [thread overview]
Message-ID: <20240719091959.17163-2-jacky_gam_2001@163.com> (raw)
In-Reply-To: <20240719091959.17163-1-jacky_gam_2001@163.com>
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@163.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
next prev parent reply other threads:[~2024-07-19 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 9:19 [PATCH v3 0/2] nvmet: use unbound_wq for RDMA and TCP " Ping Gan
2024-07-19 9:19 ` Ping Gan [this message]
2024-07-19 9:19 ` [PATCH v3 2/2] nvmet-rdma: use unbound_wq for nvmet-rdma " Ping Gan
2024-07-21 11:03 ` [PATCH v3 0/2] nvmet: use unbound_wq for RDMA and TCP " Sagi Grimberg
2024-07-26 2:34 ` Ping Gan
2024-07-27 19:36 ` [PATCH " Sagi Grimberg
2024-07-31 7:03 ` Ping Gan
2024-07-31 7:36 ` Sagi Grimberg
2024-08-02 3:39 ` [PATCH v30/2] " Ping Gan
2024-08-04 6:53 ` Sagi Grimberg
2024-08-06 10:08 ` Re :[PATCH v3 0/2] " Ping Gan
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=20240719091959.17163-2-jacky_gam_2001@163.com \
--to=jacky_gam_2001@163.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ping.gan@dell.com \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®