From: Ping Gan <jacky_gam_2001@163.com>
To: 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 0/2] nvmet: support polling task for RDMA and TCP
Date: Wed, 26 Jun 2024 16:28:21 +0800 [thread overview]
Message-ID: <20240626082823.48326-1-jacky_gam_2001@163.com> (raw)
When running nvmf on SMP platform, current nvme target's RDMA and
TCP use kworker to handle IO. But if there is other high workload
in the system(eg: on kubernetes), the competition between the
kworker and other workload is very radical. And since the kworker
is scheduled by OS randomly, it's difficult to control OS resource
and also tune the performance. If target support to use delicated
polling task to handle IO, it's useful to control OS resource and
gain good performance. So it makes sense to add polling task in
rdma-rdma and rdma-tcp modules.
Ping Gan (2):
nvmet-rdma: add polling cq task for nvmet-rdma
nvmet-tcp: add polling task for nvmet-tcp
drivers/nvme/target/rdma.c | 331 +++++++++++++++++++++++++++++++++-
drivers/nvme/target/tcp.c | 356 +++++++++++++++++++++++++++++++++++--
2 files changed, 665 insertions(+), 22 deletions(-)
--
2.26.2
next reply other threads:[~2024-06-26 8:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 8:28 Ping Gan [this message]
2024-06-26 8:28 ` [PATCH 1/2] nvmet-rdma: add polling cq task for nvmet-rdma Ping Gan
2024-06-26 8:28 ` [PATCH 2/2] nvmet-tcp: add polling task for nvmet-tcp Ping Gan
2024-06-30 8:58 ` [PATCH 0/2] nvmet: support polling task for RDMA and TCP Sagi Grimberg
2024-07-01 7:42 ` Ping Gan
2024-07-01 7:42 ` Ping Gan
2024-07-01 8:22 ` Sagi Grimberg
2024-07-02 10:02 ` Ping Gan
2024-07-02 10:02 ` Ping Gan
2024-07-03 19:58 ` Sagi Grimberg
2024-07-04 8:10 ` Ping Gan
2024-07-04 8:40 ` Sagi Grimberg
2024-07-04 10:35 ` Ping Gan
2024-07-05 5:59 ` Sagi Grimberg
2024-07-05 6:28 ` Ping Gan
2024-07-16 10:36 ` Hannes Reinecke
2024-07-17 0:53 ` 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=20240626082823.48326-1-jacky_gam_2001@163.com \
--to=jacky_gam_2001@163.com \
--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