diff options
| author | Jeff Layton <jlayton@primarydata.com> | 2014-09-19 10:53:47 -0400 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2014-09-19 11:16:16 -0400 |
| commit | 54f9bfeec7e68ef4b9be4fc70f17c9b9350637b4 (patch) | |
| tree | a7fd1c479f1bc9afda50040c218d428a29f31c30 /support/export/export.c | |
| parent | 64229ea3c8506a9b0599eafffa3d6bb488c248ec (diff) | |
| download | nfs-utils-54f9bfeec7e68ef4b9be4fc70f17c9b9350637b4.tar.gz nfs-utils-54f9bfeec7e68ef4b9be4fc70f17c9b9350637b4.tar.xz nfs-utils-54f9bfeec7e68ef4b9be4fc70f17c9b9350637b4.zip | |
sm-notify: inform the kernel if there were no hosts to notify
In the event that there no hosts to be notified after a reboot, there's
no real reason to force lockd to wait the entire grace period before
handing out locks. We're not expecting any reclaim requests to come in
that situation.
Have sm-notify do a write to /proc/fs/lockd/nlm_end_grace if that file
is present. That informs the kernel that it's OK to go ahead and lift
lockd's grace period early.
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'support/export/export.c')
0 files changed, 0 insertions, 0 deletions