On Wed, Jul 17, 2024 at 05:14:49PM +0800, Ping Gan wrote:I'd be happy to switch to unbound workqueues per default.
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 enable 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.
So why aren't we using unbound workqueues by default? Who makea the
policy decision and how does anyone know which one to chose?