diff options
| author | Jeff Layton <jlayton@poochiereds.net> | 2015-08-20 13:17:01 +0200 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2015-08-31 22:32:14 +0200 |
| commit | 51a545685905c934237e640083bc3aa40b36dc14 (patch) | |
| tree | 48d60e6307a4c5e9ddb291633de83499721f460b /fs/nfsd | |
| parent | nfsd: don't WARN/backtrace for invalid container deployment. (diff) | |
| download | linux-51a545685905c934237e640083bc3aa40b36dc14.tar.xz linux-51a545685905c934237e640083bc3aa40b36dc14.zip | |
nfsd: allow more than one laundry job to run at a time
We can potentially have several nfs4_laundromat jobs running if there
are multiple namespaces running nfsd on the box. Those are effectively
separated from one another though, so I don't see any reason to
serialize them.
Also, create_singlethread_workqueue automatically adds the
WQ_MEM_RECLAIM flag. Since we run this job on a timer, it's not really
involved in any reclaim paths. I see no need for a rescuer thread.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd')
| -rw-r--r-- | fs/nfsd/nfs4state.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c index c0c47a878cc6..af88d1d7ccae 100644 --- a/fs/nfsd/nfs4state.c +++ b/fs/nfsd/nfs4state.c @@ -6598,7 +6598,7 @@ nfs4_state_start(void) ret = set_callback_cred(); if (ret) return -ENOMEM; - laundry_wq = create_singlethread_workqueue("nfsd4"); + laundry_wq = alloc_workqueue("%s", WQ_UNBOUND, 0, "nfsd4"); if (laundry_wq == NULL) { ret = -ENOMEM; goto out_recovery; |