Re: [PATCH v3 0/2] nvmet: use unbound_wq for RDMA and TCP by default

From: Sagi Grimberg
Date: Sun Jul 21 2024 - 07:03:55 EST





On 19/07/2024 12:19, Ping Gan wrote:
When running nvmf on SMP platform, current nvme target's RDMA and
TCP use bounded workqueue to handle IO, but when there is other high
workload on the system(eg: kubernetes), the competition between the
bounded kworker and other workload is very radical. To decrease the
resource race of OS among them, this patchset will switch to unbounded
workqueue for nvmet-rdma and nvmet-tcp; besides that, it can also
get some performance improvement. And this patchset bases on previous
discussion from below session.

https://lore.kernel.org/lkml/20240719084953.8050-1-jacky_gam_2001@xxxxxxx/

Hold your horses.

This cannot be just switched without a thorough testing and actual justification/proof of
a benefit beyond just a narrow use-case brought initially by Ping Gan.

If the ask is to universally use an unbound workqueue, please provide detailed
benchmarking convincing us that this makes sense.