diff options
| author | Olga Kornievskaia <aglo@umich.edu> | 2017-06-29 09:25:36 -0400 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2018-02-08 16:24:35 -0500 |
| commit | f515f86b34b2e7d4b24cc9b7375c9e749895088e (patch) | |
| tree | 8f39d79722093381684830f6f9a1b13f702abfe9 /net/sunrpc/sched.c | |
| parent | 90ea9f1b60c679049619a79d9fc1557bc41c4973 (diff) | |
| download | linux-f515f86b34b2e7d4b24cc9b7375c9e749895088e.tar.gz linux-f515f86b34b2e7d4b24cc9b7375c9e749895088e.tar.bz2 linux-f515f86b34b2e7d4b24cc9b7375c9e749895088e.zip | |
fix parallelism for rpc tasks
Hi folks,
On a multi-core machine, is it expected that we can have parallel RPCs
handled by each of the per-core workqueue?
In testing a read workload, observing via "top" command that a single
"kworker" thread is running servicing the requests (no parallelism).
It's more prominent while doing these operations over krb5p mount.
What has been suggested by Bruce is to try this and in my testing I
see then the read workload spread among all the kworker threads.
Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'net/sunrpc/sched.c')
| -rw-r--r-- | net/sunrpc/sched.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/net/sunrpc/sched.c b/net/sunrpc/sched.c index 25e6051e97f2..d9db2eab3a8d 100644 --- a/net/sunrpc/sched.c +++ b/net/sunrpc/sched.c @@ -1104,7 +1104,7 @@ static int rpciod_start(void) * Create the rpciod thread and wait for it to start. */ dprintk("RPC: creating workqueue rpciod\n"); - wq = alloc_workqueue("rpciod", WQ_MEM_RECLAIM, 0); + wq = alloc_workqueue("rpciod", WQ_MEM_RECLAIM | WQ_UNBOUND, 0); if (!wq) goto out_failed; rpciod_workqueue = wq; |