Searched hist:"8658452 e4a588da603f6cb5ee2615deafcd82b71" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/nfsd/ |
| H A D | nfssvc.c | diff 8658452e4a588da603f6cb5ee2615deafcd82b71 Sun May 11 20:22:47 CDT 2014 NeilBrown <neilb@suse.de> nfsd: Only set PF_LESS_THROTTLE when really needed.
PF_LESS_THROTTLE has a very specific use case: to avoid deadlocks
and live-locks while writing to the page cache in a loop-back
NFS mount situation.
It therefore makes sense to *only* set PF_LESS_THROTTLE in this
situation.
We now know when a request came from the local-host so it could be a
loop-back mount. We already know when we are handling write requests,
and when we are doing anything else.
So combine those two to allow nfsd to still be throttled (like any
other process) in every situation except when it is known to be
problematic.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|
| H A D | vfs.c | diff 8658452e4a588da603f6cb5ee2615deafcd82b71 Sun May 11 20:22:47 CDT 2014 NeilBrown <neilb@suse.de> nfsd: Only set PF_LESS_THROTTLE when really needed.
PF_LESS_THROTTLE has a very specific use case: to avoid deadlocks
and live-locks while writing to the page cache in a loop-back
NFS mount situation.
It therefore makes sense to *only* set PF_LESS_THROTTLE in this
situation.
We now know when a request came from the local-host so it could be a
loop-back mount. We already know when we are handling write requests,
and when we are doing anything else.
So combine those two to allow nfsd to still be throttled (like any
other process) in every situation except when it is known to be
problematic.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|