nfsd: open file caching
Subsystems (8)
v5 cover nfsd: open file caching
v5:
- switch to using flush_delayed_fput instead of __fput_sync
- hash on inode->i_ino instead of inode pointer
- add /proc/fs/nfsd/file_cache_stats file to track stats on the hash
- eliminate extra fh_verify in nfsd_file_acquire
v4:
- squash some of the patches down into one patch to reduce churn
- close cached open files after unlink instead of before
- don't just close files after nfsd does an unlink, must do it after any vfs-layer unlink. Use fsnotify to handle that.
- use a SRCU notifier chain for setlease
- add patch to allow non-kthreads to do a fput_sync
v3:
- open files are now hashed on inode pointer instead of fh
- eliminate the recurring workqueue job in favor of shrinker/LRU and notifier from lease setting code
- have nfsv4 use the cache as well
- removal of raparms cache
v2:
- changelog cleanups and clarifications
- allow COMMIT to use cached open files
- tracepoints for nfsd_file cache
- proactively close open files prior to REMOVE, or a RENAME over a positive dentry
This is the fifth iteration of the open file cache patches for nfsd. The main changes from the v4 set are the conversion of the code to use flush_delayed_fput instead of __fput_sync, and some changes to improve performance.
The kbuild test robot noted a drop in performance with this set, which turned out to be lousy hash distribution due to hashing on inode pointer value. Hashing on inode->i_ino gives a much better distribution.
For those seeing this for the first time, main impetus here is to help speed up NFSv3 I/O. nfsd will do an open+read/write+close for every READ or WRITE RPC. This patchset allows us to cache those open files more or less indefinitely, and close them out in response to certain vfs-layer activity (unlinks and setlease attempts primarily).
The first few patches in the series make (small) changes to several subsystems to enable the caching infrastructure. The tenth patch adds the cache itself, and then the remaining patches hook the nfsd code up to the cache. The final patch rips out the raparms cache since it's no longer needed with these changes.
Again, the most controversial part of the set is probably the changes to allow normal user processes to use the delayed_fput infrastructure. Al, if you could weigh in on those, then that would be helpful. We really do need a way to allow a thread to flush the final fput work without returning to userland.
Jeff Layton (20):
list_lru: add list_lru_rotate
fs: have flush_delayed_fput flush the workqueue job
fs: add a kerneldoc header to fput
fs: add fput_queue
fs: export flush_delayed_fput
fsnotify: export several symbols
locks: create a new notifier chain for lease attempts
nfsd: move include of state.h from trace.c to trace.h
sunrpc: add a new cache_detail operation for when a cache is flushed
nfsd: add a new struct file caching facility to nfsd
nfsd: keep some rudimentary stats on nfsd_file cache
nfsd: allow filecache open to skip fh_verify check
nfsd: hook up nfsd_write to the new nfsd_file cache
nfsd: hook up nfsd_read to the nfsd_file cache
nfsd: hook nfsd_commit up to the nfsd_file cache
nfsd: convert nfs4_file->fi_fds array to use nfsd_files
nfsd: have nfsd_test_lock use the nfsd_file cache
nfsd: convert fi_deleg_file and ls_file fields to nfsd_file
nfsd: hook up nfs4_preprocess_stateid_op to the nfsd_file cache
nfsd: rip out the raparms cache
fs/file_table.c | 76 +++++- fs/locks.c | 37 +++ fs/nfsd/Kconfig | 2 + fs/nfsd/Makefile | 3 +- fs/nfsd/export.c | 14 + fs/nfsd/filecache.c | 613 +++++++++++++++++++++++++++++++++++++++++++ fs/nfsd/filecache.h | 38 +++ fs/nfsd/nfs3proc.c | 2 +- fs/nfsd/nfs4layouts.c | 12 +- fs/nfsd/nfs4proc.c | 32 +-- fs/nfsd/nfs4state.c | 174 ++++++------ fs/nfsd/nfs4xdr.c | 16 +- fs/nfsd/nfsctl.c | 10 + fs/nfsd/nfsproc.c | 2 +- fs/nfsd/nfssvc.c | 16 +- fs/nfsd/state.h | 10 +- fs/nfsd/trace.c | 2 - fs/nfsd/trace.h | 129 +++++++++ fs/nfsd/vfs.c | 269 +++++-------------- fs/nfsd/vfs.h | 11 +- fs/nfsd/xdr4.h | 15 +- fs/notify/group.c | 2 + fs/notify/mark.c | 3 + include/linux/file.h | 1 + include/linux/fs.h | 1 + include/linux/list_lru.h | 13 + include/linux/sunrpc/cache.h | 1 + mm/list_lru.c | 15 ++ net/sunrpc/cache.c | 3 + 29 files changed, 1149 insertions(+), 373 deletions(-) create mode 100644 fs/nfsd/filecache.c create mode 100644 fs/nfsd/filecache.h
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 1444042962-6947-1-git-send-email-jeff.layton-7I+n7zu2hftEKMMhf/[email protected]
PATCH v5 5/20 fs: export flush_delayed_fput
...and clean up the comments over it a bit. The nfsd code will need to be able to call back into this.
--- fs/file_table.c | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-)
fs/file_table.c +13 -9
@@ -246,20 +246,24 @@ static void ____fput(struct callback_head *work) static DECLARE_DELAYED_WORK(delayed_fput_work, delayed_fput); -/* -* If kernel thread really needs to have the final fput() it has done -* to complete, call this. The only user right now is the boot - we -* *do* need to make sure our writes to binaries on initramfs has -* not left us with opened struct file waiting for __fput() - execve() -* won't work without that. Please, don't add more callers without -* very good reasons; in particular, never call that with locks -* held and never call that from a thread that might need to do -* some work on any kind of umount. +/** +* flush_delayed_fput - ensure that all delayed_fput work is complete +* +* If kernel thread or task that has used fput_queue really needs to have the +* final fput() it has done to complete, call this. One of the main users is +* the boot - we *do* need to make sure our writes to binaries on initramfs has +* not left us with opened struct file waiting for __fput() - execve() won't +* work without that. +* +* Please, don't add more callers without very good reasons; in particular, +* never call that with locks held and never from a thread that might need to +* do some work on any kind of umount. */ void flush_delayed_fput (void ) {flush_delayed_work (&delayed_fput_work); } +EXPORT_SYMBOL (flush_delayed_fput);/** * fput - put a struct file reference
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 6/20 fsnotify: export several symbols
In reply to a message not in the archiveWith nfsd's new open-file caching infrastructure, we need a way to know when unlinks occur so it can close files that it may be holding open. fsnotify fits the bill nicely, but the symbols aren't currently exported to modules. Export some of its symbols so nfsd can use this infrastructure.
--- fs/notify/group.c | 2 ++ fs/notify/mark.c | 3 +++ 2 files changed, 5 insertions(+)
fs/notify/group.c +2 -0
@@ -81,6 +81,7 @@ void fsnotify_put_group(struct fsnotify_group *group)if (atomic_dec_and_test (&group->refcnt))fsnotify_final_destroy_group (group); } +EXPORT_SYMBOL_GPL (fsnotify_put_group);/* * Create a new fsnotify_group and hold a reference for the group returned.
@@ -109,6 +110,7 @@ struct fsnotify_group *fsnotify_alloc_group(const struct fsnotify_ops *ops)return group; } +EXPORT_SYMBOL_GPL (fsnotify_alloc_group);int fsnotify_fasync (int fd,struct file *file,int on) {
fs/notify/mark.c +3 -0
@@ -208,6 +208,7 @@ void fsnotify_destroy_mark(struct fsnotify_mark *mark,mutex_unlock (&group->mark_mutex);fsnotify_free_mark (mark); } +EXPORT_SYMBOL_GPL (fsnotify_destroy_mark);void fsnotify_destroy_marks (struct hlist_head *head,spinlock_t *lock) {
@@ -402,6 +403,7 @@ int fsnotify_add_mark(struct fsnotify_mark *mark, struct fsnotify_group *group,mutex_unlock (&group->mark_mutex);return ret; } +EXPORT_SYMBOL_GPL (fsnotify_add_mark);/* * Given a list of marks, find the mark associated with given group. If found
@@ -492,6 +494,7 @@ void fsnotify_init_mark(struct fsnotify_mark *mark,atomic_set (&mark->refcnt,1 ); mark->free_mark = free_mark; } +EXPORT_SYMBOL_GPL (fsnotify_init_mark);static int fsnotify_mark_destroy (void *ignored) {
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 8/20 nfsd: move include of state.h from trace.c to trace.h
In reply to a message not in the archiveAny file which includes trace.h will need to include state.h, even if they aren't using any state tracepoints. Ensure that we include any headers that might be needed in trace.h instead of relying on the *.c files to have the right ones.
--- fs/nfsd/trace.c | 2 -- fs/nfsd/trace.h | 2 ++ 2 files changed, 2 insertions(+), 2 deletions(-)
fs/nfsd/trace.c +0 -2
@@ -1,5 +1,3 @@ -#include "state.h" -#define CREATE_TRACE_POINTS #include "trace.h"
fs/nfsd/trace.h +2 -0
@@ -9,6 +9,8 @@#include <linux/tracepoint.h> +#include "state.h" + DECLARE_EVENT_CLASS(nfsd_stateid_class, TP_PROTO(stateid_t *stp), TP_ARGS(stp),
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 12/20 nfsd: allow filecache open to skip fh_verify check
In reply to a message not in the archiveCurrently, we call fh_verify twice on the filehandle. Once when we call into nfsd_file_acquire, and then again from nfsd_open. The second one is completely superfluous though, and fh_verify can do some things that require a fair bit of work (checking permissions, for instance).
Create a new nfsd_open_verified function that will do an nfsd_open on a filehandle that has already been verified. Call that from the filecache code.
--- fs/nfsd/filecache.c | 2 +- fs/nfsd/vfs.c | 63 +++++++++++++++++++++++++++++++++++------------------ fs/nfsd/vfs.h | 2 ++ 3 files changed, 45 insertions(+), 22 deletions(-)
fs/nfsd/filecache.c +1 -1
@@ -572,7 +572,7 @@ out:return status; open_file:/* FIXME: should we abort opening if the link count goes to 0? */ - status =nfsd_open (rqstp, fhp,S_IFREG , may_flags, &nf->nf_file); + status =nfsd_open_verified (rqstp, fhp,S_IFREG , may_flags, &nf->nf_file);clear_bit_unlock (NFSD_FILE_PENDING , &nf->nf_flags);smp_mb__after_atomic ();wake_up_bit (&nf->nf_flags,NFSD_FILE_PENDING );
fs/nfsd/vfs.c +42 -21
81 lines not on this page · raw message
fs/nfsd/vfs.h +2 -0
@@ -72,6 +72,8 @@ __be32 nfsd_commit(struct svc_rqst *, struct svc_fh *,int nfsd_open_break_lease (struct inode *,int );__be32 nfsd_open (struct svc_rqst *,struct svc_fh *,umode_t ,int ,struct file **); +__be32 nfsd_open_verified (struct svc_rqst *,struct svc_fh *,umode_t , +int ,struct file **);struct raparms ;__be32 nfsd_splice_read (struct svc_rqst *,struct file *,loff_t ,unsigned long *);
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 13/20 nfsd: hook up nfsd_write to the new nfsd_file cache
In reply to a message not in the archiveNote that all callers currently pass in NULL for "file" anyway, so there was already some dead code in here. Just eliminate that parm and have it use the file cache instead of dealing directly with a filp.
--- fs/nfsd/nfs3proc.c | 2 +- fs/nfsd/nfsproc.c | 2 +- fs/nfsd/vfs.c | 33 +++++++++++---------------------- fs/nfsd/vfs.h | 2 +- 4 files changed, 14 insertions(+), 25 deletions(-)
fs/nfsd/nfs3proc.c +1 -1
@@ -192,7 +192,7 @@ nfsd3_proc_write(struct svc_rqst *rqstp, struct nfsd3_writeargs *argp,fh_copy (&resp->fh, &argp->fh); resp->committed = argp->stable; - nfserr = nfsd_write(rqstp, &resp->fh, NULL, + nfserr = nfsd_write(rqstp, &resp->fh, argp->offset, rqstp->rq_vec, argp->vlen, &cnt,
fs/nfsd/nfsproc.c +1 -1
@@ -213,7 +213,7 @@ nfsd_proc_write(struct svc_rqst *rqstp, struct nfsd_writeargs *argp,SVCFH_fmt (&argp->fh), argp->len, argp->offset); - nfserr = nfsd_write(rqstp, fh_copy(&resp->fh, &argp->fh), NULL, + nfserr = nfsd_write(rqstp, fh_copy(&resp->fh, &argp->fh), argp->offset, rqstp->rq_vec, argp->vlen, &cnt,
fs/nfsd/vfs.c +11 -22
@@ -42,6 +42,7 @@#include "nfsd.h" #include "vfs.h" +#include "filecache.h" #define NFSDDBG_FACILITY NFSDDBG_FILEOP
@@ -1030,30 +1031,18 @@ __be32 nfsd_read(struct svc_rqst *rqstp, struct svc_fh *fhp,* N.B. After this call fhp needs an fh_put */ __be32 -nfsd_write (struct svc_rqst *rqstp,struct svc_fh *fhp,struct file *file, -loff_t offset,struct kvec *vec,int vlen,unsigned long *cnt, -int *stablep) +nfsd_write (struct svc_rqst *rqstp,struct svc_fh *fhp,loff_t offset, +struct kvec *vec,int vlen,unsigned long *cnt,int *stablep) { -__be32 err =0 ; - -if (file) { - err =nfsd_permission (rqstp, fhp->fh_export, fhp->fh_dentry, -NFSD_MAY_WRITE |NFSD_MAY_OWNER_OVERRIDE ); -if (err) - goto out; - err =nfsd_vfs_write (rqstp, fhp, file, offset, vec, vlen, cnt, - stablep); - }else { - err =nfsd_open (rqstp, fhp,S_IFREG ,NFSD_MAY_WRITE , &file); -if (err) - goto out; - -if (cnt) - err =nfsd_vfs_write (rqstp, fhp, file, offset, vec, vlen, - cnt, stablep); -fput (file); +__be32 err; +struct nfsd_file *nf; + + err =nfsd_file_acquire (rqstp, fhp,NFSD_MAY_WRITE , &nf); +if (err == nfs_ok) { + err =nfsd_vfs_write (rqstp, fhp, nf->nf_file, offset, vec, + vlen, cnt, stablep); +nfsd_file_put (nf); } -out:return err; }
fs/nfsd/vfs.h +1 -1
@@ -81,7 +81,7 @@ __be32 nfsd_readv(struct file *, loff_t, struct kvec *, int, unsigned long *);__be32 nfsd_read (struct svc_rqst *,struct svc_fh *,loff_t ,struct kvec *,int ,unsigned long *); -__be32 nfsd_write (struct svc_rqst *,struct svc_fh *,struct file *, +__be32 nfsd_write (struct svc_rqst *,struct svc_fh *,loff_t ,struct kvec *,int ,unsigned long *,int *); __be32 nfsd_vfs_write(struct svc_rqst *rqstp, struct svc_fh *fhp, struct file *file, loff_t offset,
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 14/20 nfsd: hook up nfsd_read to the nfsd_file cache
In reply to a message not in the archive--- fs/nfsd/vfs.c | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-)
fs/nfsd/vfs.c +8 -13
@@ -1008,20 +1008,15 @@ out_nfserr:__be32 nfsd_read (struct svc_rqst *rqstp,struct svc_fh *fhp,loff_t offset,struct kvec *vec,int vlen,unsigned long *count) { -struct file *file; -struct raparms *ra; -__be32 err; - - err =nfsd_open (rqstp, fhp,S_IFREG ,NFSD_MAY_READ , &file); -if (err) -return err; - - ra =nfsd_init_raparms (file); - err =nfsd_vfs_read (rqstp, file, offset, vec, vlen, count); -if (ra) -nfsd_put_raparams (file, ra); -fput (file); +__be32 err; +struct nfsd_file *nf; + err =nfsd_file_acquire (rqstp, fhp,NFSD_MAY_READ , &nf); +if (err == nfs_ok) { + err =nfsd_vfs_read (rqstp, nf->nf_file, offset, vec, vlen, + count); +nfsd_file_put (nf); + }return err; }
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 18/20 nfsd: convert fi_deleg_file and ls_file fields to nfsd_file
In reply to a message not in the archiveHave them keep an nfsd_file reference instead of a struct file.
--- fs/nfsd/nfs4layouts.c | 12 ++--- fs/nfsd/nfs4state.c | 131 ++++++++++++++++++++++++++------------------------ fs/nfsd/state.h | 6 +-- 3 files changed, 76 insertions(+), 73 deletions(-)
fs/nfsd/nfs4layouts.c +6 -6
@@ -144,8 +144,8 @@ nfsd4_free_layout_stateid(struct nfs4_stid *stid)list_del_init (&ls->ls_perfile);spin_unlock (&fp->fi_lock); -vfs_setlease (ls->ls_file,F_UNLCK ,NULL , (void **)&ls); -fput (ls->ls_file); +vfs_setlease (ls->ls_file->nf_file,F_UNLCK ,NULL , (void **)&ls); +nfsd_file_put (ls->ls_file);if (ls->ls_recalled)atomic_dec (&ls->ls_stid.sc_file->fi_lo_recalls);
@@ -169,7 +169,7 @@ nfsd4_layout_setlease(struct nfs4_layout_stateid *ls) fl->fl_end =OFFSET_MAX ; fl->fl_owner = ls; fl->fl_pid = current->tgid; - fl->fl_file = ls->ls_file; + fl->fl_file = ls->ls_file->nf_file; status =vfs_setlease (fl->fl_file, fl->fl_type, &fl,NULL );if (status) {
@@ -207,13 +207,13 @@ nfsd4_alloc_layout_stateid(struct nfsd4_compound_state *cstate, NFSPROC4_CLNT_CB_LAYOUT);if (parent->sc_type ==NFS4_DELEG_STID ) - ls->ls_file =get_file (fp->fi_deleg_file); + ls->ls_file =nfsd_file_get (fp->fi_deleg_file);else ls->ls_file =find_any_file (fp);BUG_ON (!ls->ls_file);if (nfsd4_layout_setlease (ls)) { -fput (ls->ls_file); +nfsd_file_put (ls->ls_file);put_nfs4_file (fp);kmem_cache_free (nfs4_layout_stateid_cache, ls);return NULL ;
@@ -598,7 +598,7 @@ nfsd4_cb_layout_fail(struct nfs4_layout_stateid *ls) argv[0 ] ="/sbin/nfsd-recall-failed" ; argv[1 ] = addr_str; - argv[2 ] = ls->ls_file->f_path.mnt->mnt_sb->s_id; + argv[2 ] = ls->ls_file->nf_file->f_path.mnt->mnt_sb->s_id; argv[3 ] =NULL ; error =call_usermodehelper (argv[0 ], argv, envp,UMH_WAIT_PROC );
fs/nfsd/nfs4state.c +67 -64
353 lines not on this page · raw message
fs/nfsd/state.h +3 -3
@@ -501,7 +501,7 @@ struct nfs4_file {*/ atomic_t fi_access[2 ];u32 fi_share_deny; -struct file *fi_deleg_file; +struct nfsd_file *fi_deleg_file;int fi_delegees;struct knfsd_fh fi_fhandle;bool fi_had_conflict;
@@ -550,7 +550,7 @@ struct nfs4_layout_stateid {spinlock_t ls_lock;struct list_head ls_layouts;u32 ls_layout_type; -struct file *ls_file; +struct nfsd_file *ls_file;struct nfsd4_callback ls_recall;stateid_t ls_recall_sid;bool ls_recalled;
@@ -615,7 +615,7 @@ static inline void get_nfs4_file(struct nfs4_file *fi) {atomic_inc (&fi->fi_ref); } -struct file *find_any_file (struct nfs4_file *f); +struct nfsd_file *find_any_file (struct nfs4_file *f);/* grace period management */ void nfsd4_end_grace (struct nfsd_net *nn);
Signature · 6 lines
2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
I get a this on the client running some lease tests:
[ 38.552120] BUG: unable to handle kernel NULL pointer dereference at (null) [ 38.552723] IP: [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.553111] PGD 56c2d067 PUD 51145067 PMD 0 [ 38.553534] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 38.554128] Modules linked in: nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc [ 38.555102] CPU: 0 PID: 4890 Comm: lease_tests Not tainted 4.3.0-rc3-14186-g7619b8e #322 [ 38.555593] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 [ 38.556005] task: ffff880075bd8080 ti: ffff880055560000 task.ti: ffff880055560000 [ 38.556005] RIP: 0010:[<ffffffff811fcb3f>] [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.556005] RSP: 0018:ffff880055563e98 EFLAGS: 00010246 [ 38.556005] RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffff880055563ec8 [ 38.556005] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff880051133e40 [ 38.556005] RBP: ffff880055563eb8 R08: 0000000000000000 R09: 00007ffc941da360 [ 38.556005] R10: 0000000000000008 R11: 0000000000000212 R12: ffff880051133e40 [ 38.556005] R13: 0000000000000000 R14: ffff880051133e40 R15: ffff880051133e40 [ 38.556005] FS: 00007fbbe6864700(0000) GS:ffff88007f800000(0000) knlGS:0000000000000000 [ 38.556005] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 38.556005] CR2: 0000000000000000 CR3: 00000000590b0000 CR4: 00000000000406f0 [ 38.556005] Stack: [ 38.556005] ffff880056dd1f88 0000000000000002 0000000000000400 0000000000000002 [ 38.556005] ffff880055563ef8 ffffffff811fd4c1 ffff880051133e40 ffffffff8157b913 [ 38.556005] 0000000000000000 0000000000000000 0000000000000400 0000000000000002 [ 38.556005] Call Trace: [ 38.556005] [<ffffffff811fd4c1>] fcntl_setlease+0xa1/0xd0 [ 38.556005] [<ffffffff8157b913>] ? security_file_fcntl+0x43/0x60 [ 38.556005] [<ffffffff811bc74f>] SyS_fcntl+0x31f/0x630 [ 38.556005] [<ffffffff81a77117>] entry_SYSCALL_64_fastpath+0x12/0x6f [ 38.556005] Code: ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 49 89 d5 49 89 fc 48 89 f3 48 83 ec 08 48 83 fe 02 <48> 8b 12 74 14 48 c7 c7 40 cb 27 83 48 89 4d e0 e8 9c d8 e9 ff [ 38.556005] RIP [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.556005] RSP <ffff880055563e98> [ 38.556005] CR2: 0000000000000000 [ 38.573673] ---[ end trace 2e6e1d4b9df8a11e ]---
--b.
Quoted 102 lines · Jeff Layton
v5:
- switch to usingflush_delayed_fputinstead of__fput_sync
- hash oninode->i_inoinstead of inode pointer
- add/proc/fs/nfsd/file_cache_statsfile to track stats on the hash
- eliminate extrafh_verifyinnfsd_file_acquirev4:
- squash some of the patches down into one patch to reduce churn
- close cached open files after unlink instead of before
- don't just close files after nfsd does an unlink, must do it after any vfs-layer unlink. Use fsnotify to handle that.
- use a SRCU notifier chain for setlease
- add patch to allow non-kthreads to do afput_syncv3:
- open files are now hashed on inode pointer instead of fh
- eliminate the recurring workqueue job in favor of shrinker/LRU and notifier from lease setting code
- have nfsv4 use the cache as well
- removal of raparms cachev2:
- changelog cleanups and clarifications
- allow COMMIT to use cached open files
- tracepoints fornfsd_filecache
- proactively close open files prior to REMOVE, or a RENAME over a positive dentryThis is the fifth iteration of the open file cache patches for nfsd. The main changes from the v4 set are the conversion of the code to use
flush_delayed_fputinstead of__fput_sync, and some changes to improve performance.The kbuild test robot noted a drop in performance with this set, which turned out to be lousy hash distribution due to hashing on inode pointer value. Hashing on
inode->i_inogives a much better distribution.For those seeing this for the first time, main impetus here is to help speed up NFSv3 I/O. nfsd will do an open+read/write+close for every READ or WRITE RPC. This patchset allows us to cache those open files more or less indefinitely, and close them out in response to certain vfs-layer activity (unlinks and setlease attempts primarily).
The first few patches in the series make (small) changes to several subsystems to enable the caching infrastructure. The tenth patch adds the cache itself, and then the remaining patches hook the nfsd code up to the cache. The final patch rips out the raparms cache since it's no longer needed with these changes.
Again, the most controversial part of the set is probably the changes to allow normal user processes to use the
delayed_fputinfrastructure. Al, if you could weigh in on those, then that would be helpful. We really do need a way to allow a thread to flush the final fput work without returning to userland.Jeff Layton (20):
list_lru: addlist_lru_rotate
fs: haveflush_delayed_fputflush the workqueue job
fs: add a kerneldoc header to fput
fs: addfput_queue
fs: exportflush_delayed_fput
fsnotify: export several symbols
locks: create a new notifier chain for lease attempts
nfsd: move include ofstate.hfromtrace.ctotrace.h
sunrpc: add a newcache_detailoperation for when a cache is flushed
nfsd: add a new struct file caching facility to nfsd
nfsd: keep some rudimentary stats onnfsd_filecache
nfsd: allow filecache open to skipfh_verifycheck
nfsd: hook upnfsd_writeto the newnfsd_filecache
nfsd: hook upnfsd_readto thenfsd_filecache
nfsd: hooknfsd_commitup to thenfsd_filecache
nfsd: convertnfs4_file->fi_fdsarray to usenfsd_files
nfsd: havenfsd_test_lockuse thenfsd_filecache
nfsd: convertfi_deleg_fileandls_filefields tonfsd_file
nfsd: hook upnfs4_preprocess_stateid_opto thenfsd_filecache
nfsd: rip out the raparms cachefs/file_table.c | 76 +++++- fs/locks.c | 37 +++ fs/nfsd/Kconfig | 2 + fs/nfsd/Makefile | 3 +- fs/nfsd/export.c | 14 + fs/nfsd/filecache.c | 613 +++++++++++++++++++++++++++++++++++++++++++ fs/nfsd/filecache.h | 38 +++ fs/nfsd/nfs3proc.c | 2 +- fs/nfsd/nfs4layouts.c | 12 +- fs/nfsd/nfs4proc.c | 32 +-- fs/nfsd/nfs4state.c | 174 ++++++------ fs/nfsd/nfs4xdr.c | 16 +- fs/nfsd/nfsctl.c | 10 + fs/nfsd/nfsproc.c | 2 +- fs/nfsd/nfssvc.c | 16 +- fs/nfsd/state.h | 10 +- fs/nfsd/trace.c | 2 - fs/nfsd/trace.h | 129 +++++++++ fs/nfsd/vfs.c | 269 +++++-------------- fs/nfsd/vfs.h | 11 +- fs/nfsd/xdr4.h | 15 +- fs/notify/group.c | 2 + fs/notify/mark.c | 3 + include/linux/file.h | 1 +
Quoted 11 lines
include/linux/fs.h | 1 + include/linux/list_lru.h | 13 + include/linux/sunrpc/cache.h | 1 + mm/list_lru.c | 15 ++ net/sunrpc/cache.c | 3 + 29 files changed, 1149 insertions(+), 373 deletions(-) create mode 100644 fs/nfsd/filecache.c create mode 100644 fs/nfsd/filecache.hSignature · 1 line
2.4.3
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 35 lines · On Thu, 8 Oct 2015 12:42:25 -0400 "J. Bruce Fields" <[email protected]>…
I get a this on the client running some lease tests:
[ 38.552120] BUG: unable to handle kernel NULL pointer dereference at (null) [ 38.552723] IP: [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.553111] PGD 56c2d067 PUD 51145067 PMD 0 [ 38.553534] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 38.554128] Modules linked in: nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc [ 38.555102] CPU: 0 PID: 4890 Comm: lease_tests Not tainted 4.3.0-rc3-14186-g7619b8e #322 [ 38.555593] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 [ 38.556005] task: ffff880075bd8080 ti: ffff880055560000 task.ti: ffff880055560000 [ 38.556005] RIP: 0010:[<ffffffff811fcb3f>] [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.556005] RSP: 0018:ffff880055563e98 EFLAGS: 00010246 [ 38.556005] RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffff880055563ec8 [ 38.556005] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff880051133e40 [ 38.556005] RBP: ffff880055563eb8 R08: 0000000000000000 R09: 00007ffc941da360 [ 38.556005] R10: 0000000000000008 R11: 0000000000000212 R12: ffff880051133e40 [ 38.556005] R13: 0000000000000000 R14: ffff880051133e40 R15: ffff880051133e40 [ 38.556005] FS: 00007fbbe6864700(0000) GS:ffff88007f800000(0000) knlGS:0000000000000000 [ 38.556005] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 38.556005] CR2: 0000000000000000 CR3: 00000000590b0000 CR4: 00000000000406f0 [ 38.556005] Stack: [ 38.556005] ffff880056dd1f88 0000000000000002 0000000000000400 0000000000000002 [ 38.556005] ffff880055563ef8 ffffffff811fd4c1 ffff880051133e40 ffffffff8157b913 [ 38.556005] 0000000000000000 0000000000000000 0000000000000400 0000000000000002 [ 38.556005] Call Trace: [ 38.556005] [<ffffffff811fd4c1>] fcntl_setlease+0xa1/0xd0 [ 38.556005] [<ffffffff8157b913>] ? security_file_fcntl+0x43/0x60 [ 38.556005] [<ffffffff811bc74f>] SyS_fcntl+0x31f/0x630 [ 38.556005] [<ffffffff81a77117>] entry_SYSCALL_64_fastpath+0x12/0x6f [ 38.556005] Code: ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 49 89 d5 49 89 fc 48 89 f3 48 83 ec 08 48 83 fe 02 <48> 8b 12 74 14 48 c7 c7 40 cb 27 83 48 89 4d e0 e8 9c d8 e9 ff [ 38.556005] RIP [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 [ 38.556005] RSP <ffff880055563e98> [ 38.556005] CR2: 0000000000000000 [ 38.573673] ---[ end trace 2e6e1d4b9df8a11e ]---
Quoted 1 line
--b.
My bad...it needs this patch. I'll roll this into the set before the next posting.
Quoted 1 line
From
9f04033dcf00f7b252f03c8782795b6a1f847991Mon Sep 17 00:00:00 2001
From: Jeff Layton <[email protected]>
Date: Thu, 8 Oct 2015 12:53:54 -0400
Subject: [PATCH] locks: "lease" pointer can be NULL
...in which case we just want to skip the notifier.
--- fs/locks.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/locks.c +2 -1
@@ -1835,7 +1835,8 @@ setlease_notifier(long arg, struct file_lock *lease)int vfs_setlease (struct file *filp,long arg,struct file_lock **lease,void **priv) { -setlease_notifier (arg, *lease); +if (lease) +setlease_notifier (arg, *lease);if (filp->f_op->setlease)return filp->f_op->setlease (filp, arg, lease, priv);else
Signature · 1 line
2.4.3
A message that is not in the archive (sent off-list or not yet received): 20151008125529.3f30308e-08S845evdOaAjSkqwZiSMmfYqLom42DlXqFh9Ls21Oc@public.gmane.org
Quoted 2 lines · Jeff Layton
My bad...it needs this patch. I'll roll this into the set before the next posting.
Oh, good, thanks.
Also, just seen on the server side--not sure what was going on at the time.
There were a ton of these:
Oct 08 12:35:07 f21-1.fieldses.org kernel: ------------[ cut here ]------------ Oct 08 12:35:07 f21-1.fieldses.org kernel: WARNING: CPU: 1 PID: 584 at lib/list_debug.c:59 __list_del_entry+0x9e/0xc0() Oct 08 12:35:07 f21-1.fieldses.org kernel: list_del corruption. prev->next should be ffff88004cb23f80, but was b6a7e8df8948e4eb Oct 08 12:35:07 f21-1.fieldses.org kernel: Modules linked in: rpcsec_gss_krb5 nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc Oct 08 12:35:07 f21-1.fieldses.org kernel: CPU: 1 PID: 584 Comm: fsnotify_mark Not tainted 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:35:07 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffffffff81f62683 ffff880071af3d50 ffffffff8160540c ffff880071af3d98 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3d88 ffffffff81077692 ffff88004cb23f80 ffffffff8109c160 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3e08 ffff880071af3e30 ffff88004cb23f70 ffff880071af3de8 Oct 08 12:35:07 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8160540c>] dump_stack+0x4e/0x82 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81077692>] warn_slowpath_common+0x82/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8109c160>] ? sort_range+0x20/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8107771c>] warn_slowpath_fmt+0x4c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8162219e>] __list_del_entry+0x9e/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef485>] fsnotify_mark_destroy+0x95/0x140 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff810baa10>] ? wait_woken+0x90/0x90 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef3f0>] ? fsnotify_put_mark+0x30/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: ---[ end trace 687abd8552e06b32 ]---
Then:
Oct 08 12:41:54 f21-1.fieldses.org kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Oct 08 12:41:54 f21-1.fieldses.org kernel: IP: [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: PGD 0 Oct 08 12:41:54 f21-1.fieldses.org kernel: Oops: 0000 [#2] PREEMPT SMP DEBUG_PAGEALLOC Oct 08 12:41:54 f21-1.fieldses.org kernel: Modules linked in: rpcsec_gss_krb5 nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc Oct 08 12:41:54 f21-1.fieldses.org kernel: CPU: 1 PID: 4360 Comm: nfsd Tainted: G B D W 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:41:54 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:41:54 f21-1.fieldses.org kernel: task: ffff880051ed8040 ti: ffff880051edc000 task.ti: ffff880051edc000 Oct 08 12:41:54 f21-1.fieldses.org kernel: RIP: 0010:[<ffffffff811fcb3f>] [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: RSP: 0018:ffff880051edfc98 EFLAGS: 00010246 Oct 08 12:41:54 f21-1.fieldses.org kernel: RAX: 0000000080000000 RBX: 0000000000000002 RCX: ffff880051edfcc8 Oct 08 12:41:54 f21-1.fieldses.org kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88004b7d8e40 Oct 08 12:41:54 f21-1.fieldses.org kernel: RBP: ffff880051edfcb8 R08: 0000000000000001 R09: 0000000000000000 Oct 08 12:41:54 f21-1.fieldses.org kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88004b7d8e40 Oct 08 12:41:54 f21-1.fieldses.org kernel: R13: 0000000000000000 R14: ffff88007c64cf80 R15: ffff880069fa5240 Oct 08 12:41:54 f21-1.fieldses.org kernel: FS: 0000000000000000(0000) GS:ffff88007f900000(0000) knlGS:0000000000000000 Oct 08 12:41:54 f21-1.fieldses.org kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 08 12:41:54 f21-1.fieldses.org kernel: CR2: 0000000000000000 CR3: 000000000220b000 CR4: 00000000000406e0 Oct 08 12:41:54 f21-1.fieldses.org kernel: Stack: Oct 08 12:41:54 f21-1.fieldses.org kernel: ffff88006dbf9ea0 ffff880051c59f18 ffff88003ed0ceb0 0000000000000001 Oct 08 12:41:54 f21-1.fieldses.org kernel: ffff880051edfcd8 ffffffffa00d6816 ffff88006dbf9e98 0000000000000000 Oct 08 12:41:54 f21-1.fieldses.org kernel: ffff880051edfd20 ffffffffa00e0811 ffffffffa00e05e5 ffff88003ed0ceb0 Oct 08 12:41:54 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00d6816>] nfs4_put_deleg_lease+0x76/0x90 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00e0811>] nfsd4_delegreturn+0x231/0x240 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00e05e5>] ? nfsd4_delegreturn+0x5/0x240 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00ca63a>] nfsd4_proc_compound+0x38a/0x660 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b4608>] nfsd_dispatch+0xb8/0x200 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00151ff>] svc_process_common+0x40f/0x620 [sunrpc] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa0015557>] svc_process+0x147/0x320 [sunrpc] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b3b71>] nfsd+0x181/0x280 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b39f5>] ? nfsd+0x5/0x280 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b39f0>] ? nfsd_destroy+0x190/0x190 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:41:54 f21-1.fieldses.org kernel: Code: ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 49 89 d5 49 89 fc 48 89 f3 48 83 ec 08 48 83 fe 02 <48> Oct 08 12:41:54 f21-1.fieldses.org kernel: RIP [<ffffffff811fcb3f>] vfs_setlease+0x1f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: RSP <ffff880051edfc98> Oct 08 12:41:54 f21-1.fieldses.org kernel: CR2: 0000000000000000 Oct 08 12:41:54 f21-1.fieldses.org kernel: ---[ end trace 687abd8552e07823 ]--- Oct 08 12:41:54 f21-1.fieldses.org kernel: BUG: sleeping function called from invalid context at include/linux/sched.h:2768 Oct 08 12:41:54 f21-1.fieldses.org kernel: in_atomic(): 0, irqs_disabled(): 1, pid: 4360, name: nfsd Oct 08 12:41:54 f21-1.fieldses.org kernel: INFO: lockdep is turned off. Oct 08 12:41:54 f21-1.fieldses.org kernel: irq event stamp: 1107102 Oct 08 12:41:54 f21-1.fieldses.org kernel: hardirqs last enabled at (1107101): [<ffffffff81a76797>] _raw_spin_unlock_irqrestore+0x57/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: hardirqs last disabled at (1107102): [<ffffffff81a76607>] _raw_spin_lock_irq+0x17/0x50 Oct 08 12:41:54 f21-1.fieldses.org kernel: softirqs last enabled at (1107096): [<ffffffff81927075>] release_sock+0x165/0x1b0 Oct 08 12:41:54 f21-1.fieldses.org kernel: softirqs last disabled at (1107094): [<ffffffff81926f44>] release_sock+0x34/0x1b0 Oct 08 12:41:54 f21-1.fieldses.org kernel: CPU: 1 PID: 4360 Comm: nfsd Tainted: G B D W 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:41:54 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:41:54 f21-1.fieldses.org kernel: ffff880051ed8040 ffff880051edf9b0 ffffffff8160540c 0000000000000000 Oct 08 12:41:54 f21-1.fieldses.org kernel: ffff880051edf9d8 ffffffff810a02de ffffffff81f0907b 0000000000000ad0 Oct 08 12:41:54 f21-1.fieldses.org kernel: 0000000000000000 ffff880051edfa00 ffffffff810a0409 ffff880051ed8040 Oct 08 12:41:54 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff8160540c>] dump_stack+0x4e/0x82 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810a02de>] ___might_sleep+0x15e/0x240 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810a0409>] __might_sleep+0x49/0x80 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81087fc4>] exit_signals+0x24/0x120 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810796a2>] do_exit+0xb2/0xbc0 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810d2345>] ? kmsg_dump+0x135/0x180 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810d2232>] ? kmsg_dump+0x22/0x180 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff8100795d>] oops_end+0x6d/0x90 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff810443ea>] no_context+0x13a/0x360 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81583edb>] ? selinux_cred_prepare+0x1b/0x30 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff8104471e>] __bad_area_nosemaphore+0x10e/0x220 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81583edb>] ? selinux_cred_prepare+0x1b/0x30 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81044843>] bad_area_nosemaphore+0x13/0x20 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81044a9c>] __do_page_fault+0x8c/0x490 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81000fc0>] ? trace_hardirqs_off_thunk+0x17/0x19 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81044eac>] do_page_fault+0xc/0x10 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81a78f52>] page_fault+0x22/0x30 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff811fcb3f>] ? vfs_setlease+0x1f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00d6816>] nfs4_put_deleg_lease+0x76/0x90 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00e0811>] nfsd4_delegreturn+0x231/0x240 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00e05e5>] ? nfsd4_delegreturn+0x5/0x240 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00ca63a>] nfsd4_proc_compound+0x38a/0x660 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b4608>] nfsd_dispatch+0xb8/0x200 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00151ff>] svc_process_common+0x40f/0x620 [sunrpc] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa0015557>] svc_process+0x147/0x320 [sunrpc] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b3b71>] nfsd+0x181/0x280 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b39f5>] ? nfsd+0x5/0x280 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffffa00b39f0>] ? nfsd_destroy+0x190/0x190 [nfsd] Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:41:54 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:41:54 f21-1.fieldses.org kernel: nfsd (4360) used greatest stack depth: 12280 bytes left Oct 08 12:42:09 f21-1.fieldses.org kernel: general protection fault: 0000 [#3] PREEMPT SMP DEBUG_PAGEALLOC Oct 08 12:42:09 f21-1.fieldses.org kernel: Modules linked in: rpcsec_gss_krb5 nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc Oct 08 12:42:09 f21-1.fieldses.org kernel: CPU: 1 PID: 4361 Comm: nfsd Tainted: G B D W 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:42:09 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:42:09 f21-1.fieldses.org kernel: task: ffff880051f20080 ti: ffff880051f24000 task.ti: ffff880051f24000 Oct 08 12:42:09 f21-1.fieldses.org kernel: RIP: 0010:[<ffffffffa00c21ce>] [<ffffffffa00c21ce>] nfsd_file_acquire+0x1ce/0x820 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: RSP: 0018:ffff880051f27ad0 EFLAGS: 00010202 Oct 08 12:42:09 f21-1.fieldses.org kernel: RAX: 5a5a5a5a5a5a5a5a RBX: ffff88003e9aaf18 RCX: 0000000000000001 Oct 08 12:42:09 f21-1.fieldses.org kernel: RDX: 0000000000000008 RSI: 00000000000003db RDI: ffffffffa00f53c4 Oct 08 12:42:09 f21-1.fieldses.org kernel: RBP: ffff880051f27b40 R08: 0000000000000000 R09: 0000000000000000 Oct 08 12:42:09 f21-1.fieldses.org kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002 Oct 08 12:42:09 f21-1.fieldses.org kernel: R13: 0000000000000000 R14: ffff88003e9aaf50 R15: 0000000000000002 Oct 08 12:42:09 f21-1.fieldses.org kernel: FS: 0000000000000000(0000) GS:ffff88007f900000(0000) knlGS:0000000000000000 Oct 08 12:42:09 f21-1.fieldses.org kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 08 12:42:09 f21-1.fieldses.org kernel: CR2: 00007f8f5903c000 CR3: 000000005d801000 CR4: 00000000000406e0 Oct 08 12:42:09 f21-1.fieldses.org kernel: Stack: Oct 08 12:42:09 f21-1.fieldses.org kernel: ffffffffa00c20c9 0000000200000000 0200000000000000 ffff880051f27b78 Oct 08 12:42:09 f21-1.fieldses.org kernel: ffff880056436e00 ffff880051ed6000 0000000000039720 00000cc400000000 Oct 08 12:42:09 f21-1.fieldses.org kernel: ffff880040e03c90 ffff88006dbf9e98 0000000000000000 ffff88006dbf9ea0 Oct 08 12:42:09 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00c20c9>] ? nfsd_file_acquire+0xc9/0x820 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00d7dc1>] nfs4_get_vfs_file+0x2e1/0x3e0 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00ddc9b>] ? nfsd4_process_open2+0x2bb/0x1400 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00ddcb4>] nfsd4_process_open2+0x2d4/0x1400 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00dd9e5>] ? nfsd4_process_open2+0x5/0x1400 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b888d>] ? fh_verify+0x15d/0x570 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b986f>] ? nfsd_lookup+0x7f/0x120 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00ca172>] nfsd4_open+0x7e2/0x920 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00c9995>] ? nfsd4_open+0x5/0x920 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00ca63a>] nfsd4_proc_compound+0x38a/0x660 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b4608>] nfsd_dispatch+0xb8/0x200 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00151ff>] svc_process_common+0x40f/0x620 [sunrpc] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa0015557>] svc_process+0x147/0x320 [sunrpc] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b3b71>] nfsd+0x181/0x280 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b39f5>] ? nfsd+0x5/0x280 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffffa00b39f0>] ? nfsd_destroy+0x190/0x190 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:42:09 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:42:09 f21-1.fieldses.org kernel: Code: ff ff 41 f7 c4 00 02 00 00 75 53 44 89 e2 d1 ea 89 d1 48 8b 53 38 83 e1 01 83 e2 04 75 0d 48 8b 53 38 83 e2 08 74 37 84 c9 74 33 <48> Oct 08 12:42:09 f21-1.fieldses.org kernel: RIP [<ffffffffa00c21ce>] nfsd_file_acquire+0x1ce/0x820 [nfsd] Oct 08 12:42:09 f21-1.fieldses.org kernel: RSP <ffff880051f27ad0> Oct 08 12:42:09 f21-1.fieldses.org kernel: ---[ end trace 687abd8552e07824 ]---
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 27 lines · On Thu, 8 Oct 2015 14:04:00 -0400 "J. Bruce Fields"…
Quoted 2 lines · Jeff Layton
My bad...it needs this patch. I'll roll this into the set before the next posting.
Oh, good, thanks.
Also, just seen on the server side--not sure what was going on at the time.
There were a ton of these:
Oct 08 12:35:07 f21-1.fieldses.org kernel: ------------[ cut here ]------------ Oct 08 12:35:07 f21-1.fieldses.org kernel: WARNING: CPU: 1 PID: 584 at lib/list_debug.c:59 __list_del_entry+0x9e/0xc0() Oct 08 12:35:07 f21-1.fieldses.org kernel: list_del corruption. prev->next should be ffff88004cb23f80, but was b6a7e8df8948e4eb Oct 08 12:35:07 f21-1.fieldses.org kernel: Modules linked in: rpcsec_gss_krb5 nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc Oct 08 12:35:07 f21-1.fieldses.org kernel: CPU: 1 PID: 584 Comm: fsnotify_mark Not tainted 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:35:07 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffffffff81f62683 ffff880071af3d50 ffffffff8160540c ffff880071af3d98 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3d88 ffffffff81077692 ffff88004cb23f80 ffffffff8109c160 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3e08 ffff880071af3e30 ffff88004cb23f70 ffff880071af3de8 Oct 08 12:35:07 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8160540c>] dump_stack+0x4e/0x82 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81077692>] warn_slowpath_common+0x82/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8109c160>] ? sort_range+0x20/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8107771c>] warn_slowpath_fmt+0x4c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8162219e>] __list_del_entry+0x9e/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef485>] fsnotify_mark_destroy+0x95/0x140
Quoted 9 lines
Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff810baa10>] ? wait_woken+0x90/0x90 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef3f0>] ? fsnotify_put_mark+0x30/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: ---[ end trace 687abd8552e06b32 ]---
Thanks for the bug report! I think I understand the problem now:
It's in the way this patchset embeds a fsnotify_mark inside the nfsd_file. The way fsnotify_destroy_mark works sort of requires that it be freed separately since it wants to traverse these objects under a srcu read lock. The rest of the stack traces are probably collateral damage from that mem corruption.
I think I'll have to change the code to allocate the fsnotify_mark objects separately. It may also be better to have just one mark per inode and have each nfsd_file take a reference to the mark. I'll need to stare at the code a bit longer to see what makes the most sense.
Signature · 5 lines
Jeff Layton <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 48 lines · Jeff Layton
Quoted 27 lines · On Thu, 8 Oct 2015 14:04:00 -0400 "J. Bruce Fields" <[email protected]>…
Quoted 2 lines · Jeff Layton
My bad...it needs this patch. I'll roll this into the set before the next posting.
Oh, good, thanks.
Also, just seen on the server side--not sure what was going on at the time.
There were a ton of these:
Oct 08 12:35:07 f21-1.fieldses.org kernel: ------------[ cut here ]------------ Oct 08 12:35:07 f21-1.fieldses.org kernel: WARNING: CPU: 1 PID: 584 at lib/list_debug.c:59 __list_del_entry+0x9e/0xc0() Oct 08 12:35:07 f21-1.fieldses.org kernel: list_del corruption. prev->next should be ffff88004cb23f80, but was b6a7e8df8948e4eb Oct 08 12:35:07 f21-1.fieldses.org kernel: Modules linked in: rpcsec_gss_krb5 nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc Oct 08 12:35:07 f21-1.fieldses.org kernel: CPU: 1 PID: 584 Comm: fsnotify_mark Not tainted 4.3.0-rc3-14186-g7619b8e #322 Oct 08 12:35:07 f21-1.fieldses.org kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffffffff81f62683 ffff880071af3d50 ffffffff8160540c ffff880071af3d98 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3d88 ffffffff81077692 ffff88004cb23f80 ffffffff8109c160 Oct 08 12:35:07 f21-1.fieldses.org kernel: ffff880071af3e08 ffff880071af3e30 ffff88004cb23f70 ffff880071af3de8 Oct 08 12:35:07 f21-1.fieldses.org kernel: Call Trace: Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8160540c>] dump_stack+0x4e/0x82 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81077692>] warn_slowpath_common+0x82/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8109c160>] ? sort_range+0x20/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8107771c>] warn_slowpath_fmt+0x4c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff8162219e>] __list_del_entry+0x9e/0xc0 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef485>] fsnotify_mark_destroy+0x95/0x140Quoted 9 lines
Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff810baa10>] ? wait_woken+0x90/0x90 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff811ef3f0>] ? fsnotify_put_mark+0x30/0x30 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098d6f>] kthread+0xef/0x110 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a767dc>] ? _raw_spin_unlock_irq+0x2c/0x50 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81a7748f>] ret_from_fork+0x3f/0x70 Oct 08 12:35:07 f21-1.fieldses.org kernel: [<ffffffff81098c80>] ? kthread_create_on_node+0x200/0x200 Oct 08 12:35:07 f21-1.fieldses.org kernel: ---[ end trace 687abd8552e06b32 ]---Thanks for the bug report! I think I understand the problem now:
It's in the way this patchset embeds a
fsnotify_markinside thenfsd_file. The wayfsnotify_destroy_markworks sort of requires that it be freed separately since it wants to traverse these objects under a srcu read lock. The rest of the stack traces are probably collateral damage from that mem corruption.
Quoted 4 lines
I think I'll have to change the code to allocate the
fsnotify_markobjects separately. It may also be better to have just one mark per inode and have eachnfsd_filetake a reference to the mark. I'll need to stare at the code a bit longer to see what makes the most sense.
OK, thanks!
--b.
PATCH v5 1/20 list_lru: add list_lru_rotate
In reply to Jeff LaytonAdd a function that can move an entry to the MRU end of the list.
--- include/linux/list_lru.h | 13 +++++++++++++ mm/list_lru.c | 15 +++++++++++++++ 2 files changed, 28 insertions(+)
include/linux/list_lru.h +13 -0
@@ -96,6 +96,19 @@ bool list_lru_add(struct list_lru *lru, struct list_head *item);bool list_lru_del (struct list_lru *lru,struct list_head *item);/** +* list_lru_rotate: rotate an element to the end of an lru list +* @list_lru: the lru pointer +* @item: the item to be rotated +* +* This function moves an entry to the end of an LRU list. Should be used when +* an entry that is on the LRU is used, and should be moved to the MRU end of +* the list. If the item is not on a list, then this function has no effect. +* The comments about an element already pertaining to a list are also valid +* for list_lru_rotate. +*/ +void list_lru_rotate (struct list_lru *lru,struct list_head *item); + +/** * list_lru_count_one: return the number of objects currently held by @lru * @lru: the lru pointer. * @nid: the node id to count from.
mm/list_lru.c +15 -0
@@ -130,6 +130,21 @@ bool list_lru_del(struct list_lru *lru, struct list_head *item) }EXPORT_SYMBOL_GPL (list_lru_del); +void list_lru_rotate (struct list_lru *lru,struct list_head *item) +{ +int nid =page_to_nid (virt_to_page (item)); +struct list_lru_node *nlru = &lru->node[nid]; +struct list_lru_one *l; + +spin_lock (&nlru->lock); +if (!list_empty (item)) { + l =list_lru_from_kmem (nlru, item); +list_move_tail (item, &l->list); + } +spin_unlock (&nlru->lock); +} +EXPORT_SYMBOL_GPL (list_lru_rotate); +void list_lru_isolate (struct list_lru_one *list,struct list_head *item) {list_del_init (item);
Signature · 1 line
2.4.3
A message that is not in the archive (sent off-list or not yet received): 1444042962-6947-2-git-send-email-jeff.layton-7I+n7zu2hftEKMMhf/[email protected]
Re: [PATCH v5 01/20] list_lru: add list_lru_rotate
Quoted 6 lines · Jeff Layton
Add a function that can move an entry to the MRU end of the list.
Cc Andrew Morton <akpm-de/[email protected]>Reviewed-by Vladimir Davydov <[email protected]>
Having read through patch 10 (nfsd: add a new struct file caching facility to nfsd) that uses this function, I think it is unnecessary as it's usage is incorrect from the perspective of the list_lru shrinker management.
What you are attempting to do is rotate the object to the tail of the LRU when the last reference is dropped, so that it gets a full trip through the LRU before being reclaimed by the shrinker. And to ensure this "works", the scan from the shrinker checks for reference counts and skip the item being isolated (i.e. return LRU_SKIP) and so leave it in it's place in the LRU.
i.e. you're attempting to manage LRU-ness of the list yourself when, in fact, the list_lru infrastructure does this and doesn't have the subtle bugs your version has. By trying to manage it yourself, the list_lru lists are no longer sorted into memory pressure driven LRU order.
e.g. your manual rotation technique means if there are nr_to_walk referenced items at the head of the list, the shrinker will skip them all and do nothing, even though there are reclaimable objects further down the list. i.e. it can't do any reclaim because it doesn't sort the list into LRU order any more.
This comes from using LRU_SKIP improperly. LRU_SKIP is there for objects that we can't lock in the isolate callback due to lock inversion issues (e.g. see dentry_lru_isolate()), and so we need to look at it again on the next scan pass. hence it gets left in place.
However, if we can lock the item and peer at it's reference counts safely and we decide that we cannot reclaim it because it is referenced, the isolate callback should be returning LRU_ROTATE to move the referenced item to the tail of the list. (Again, see dentry_lru_isolate() for an example.) The means that
the next nr_to_walk scan of the list will not rescan that item and skip it again (unless the list is very short), but will instead scan items that it hasn't yet reached.
This avoids the "shrinker does nothing due to skipped items at the head of the list" problem, and makes the LRU function as an actual LRU. i.e. referenced items all cluster towards the tail of the LRU under memory pressure and the head of the LRU contains the reclaimable objects.
So I think the correct solution is to use LRU_ROTATE correctly rather than try to manage the LRU list order externally like this.
Cheers,
Dave.
Signature · 6 lines
Dave Chinner [email protected] -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 01/20] list_lru: add list_lru_rotate
Quoted 46 lines · On Tue, 6 Oct 2015 08:47:17 +1100 Dave Chinner…
Quoted 6 lines · Jeff Layton
Add a function that can move an entry to the MRU end of the list.
Cc Andrew Morton <akpm-de/[email protected]>Reviewed-by Vladimir Davydov <[email protected]>Having read through patch 10 (nfsd: add a new struct file caching facility to nfsd) that uses this function, I think it is unnecessary as it's usage is incorrect from the perspective of the
list_lrushrinker management.What you are attempting to do is rotate the object to the tail of the LRU when the last reference is dropped, so that it gets a full trip through the LRU before being reclaimed by the shrinker. And to ensure this "works", the scan from the shrinker checks for reference counts and skip the item being isolated (i.e. return
LRU_SKIP) and so leave it in it's place in the LRU.i.e. you're attempting to manage LRU-ness of the list yourself when, in fact, the
list_lruinfrastructure does this and doesn't have the subtle bugs your version has. By trying to manage it yourself, thelist_lrulists are no longer sorted into memory pressure driven LRU order.e.g. your manual rotation technique means if there are
nr_to_walkreferenced items at the head of the list, the shrinker will skip them all and do nothing, even though there are reclaimable objects further down the list. i.e. it can't do any reclaim because it doesn't sort the list into LRU order any more.This comes from using
LRU_SKIPimproperly.LRU_SKIPis there for objects that we can't lock in the isolate callback due to lock inversion issues (e.g. seedentry_lru_isolate()), and so we need to look at it again on the next scan pass. hence it gets left in place.However, if we can lock the item and peer at it's reference counts safely and we decide that we cannot reclaim it because it is referenced, the isolate callback should be returning
LRU_ROTATEto move the referenced item to the tail of the list. (Again, seedentry_lru_isolate()for an example.) The means that
the nextnr_to_walkscan of the list will not rescan that item and skip it again (unless the list is very short), but will instead scan items that it hasn't yet reached.
Quoted 9 lines
This avoids the "shrinker does nothing due to skipped items at the head of the list" problem, and makes the LRU function as an actual LRU. i.e. referenced items all cluster towards the tail of the LRU under memory pressure and the head of the LRU contains the reclaimable objects.
So I think the correct solution is to use
LRU_ROTATEcorrectly rather than try to manage the LRU list order externally like this.
Thanks for looking, Dave. Ok, fair enough.
I grafted the LRU list stuff on after I did the original set, and I think the way I designed the refcounting doesn't really work very well with it. It has been a while since I added that in, but I do remember struggling a bit with lock inversion problems trying to do it the more standard way. It's solvable with a nfsd_file spinlock, but I wanted to avoid that -- still maybe it's the best way.
What I don't quite get conceptually is how the list_lru stuff really works...
Looking at the dcache's usage, dentry_lru_add is only called from dput and only removed from the list when you're shrinking the dcache or from __dentry_kill. It will rotate entries to the end of the list via LRU_ROTATE from the shrinker callback if DCACHE_REFERENCED was set, but I don't see how you end up with stuff at the end of the list otherwise.
So, the dcache's LRU list doesn't really seem to keep the entries in LRU order at all. It just prunes a number of entries that haven't been used since the last time the shrinker callback was called, and the rest end up staying on the list in whatever order they were originally added.
So...
dentry1 dentry2
allocated
dput
allocated
dput
found
dput again
(maybe many more times)
Now, the shrinker runs once and skips both because DCACHE_REFERENCED is set. It then runs again later and prunes dentry1 before dentry2 even though it has been used many more times since dentry2 has.
Am I missing something in how this works?
Signature · 5 lines
Jeff Layton <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20151006074341.0e2f796e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org
Re: [PATCH v5 01/20] list_lru: add list_lru_rotate
Quoted 68 lines · Jeff Layton
Quoted 46 lines · On Tue, 6 Oct 2015 08:47:17 +1100 Dave Chinner…
Quoted 6 lines · Jeff Layton
Add a function that can move an entry to the MRU end of the list.
Cc Andrew Morton <akpm-de/[email protected]>Reviewed-by Vladimir Davydov <[email protected]>Having read through patch 10 (nfsd: add a new struct file caching facility to nfsd) that uses this function, I think it is unnecessary as it's usage is incorrect from the perspective of the
list_lrushrinker management.What you are attempting to do is rotate the object to the tail of the LRU when the last reference is dropped, so that it gets a full trip through the LRU before being reclaimed by the shrinker. And to ensure this "works", the scan from the shrinker checks for reference counts and skip the item being isolated (i.e. return
LRU_SKIP) and so leave it in it's place in the LRU.i.e. you're attempting to manage LRU-ness of the list yourself when, in fact, the
list_lruinfrastructure does this and doesn't have the subtle bugs your version has. By trying to manage it yourself, thelist_lrulists are no longer sorted into memory pressure driven LRU order.e.g. your manual rotation technique means if there are
nr_to_walkreferenced items at the head of the list, the shrinker will skip them all and do nothing, even though there are reclaimable objects further down the list. i.e. it can't do any reclaim because it doesn't sort the list into LRU order any more.This comes from using
LRU_SKIPimproperly.LRU_SKIPis there for objects that we can't lock in the isolate callback due to lock inversion issues (e.g. seedentry_lru_isolate()), and so we need to look at it again on the next scan pass. hence it gets left in place.However, if we can lock the item and peer at it's reference counts safely and we decide that we cannot reclaim it because it is referenced, the isolate callback should be returning
LRU_ROTATEto move the referenced item to the tail of the list. (Again, seedentry_lru_isolate()for an example.) The means that
the nextnr_to_walkscan of the list will not rescan that item and skip it again (unless the list is very short), but will instead scan items that it hasn't yet reached.Quoted 9 lines
This avoids the "shrinker does nothing due to skipped items at the head of the list" problem, and makes the LRU function as an actual LRU. i.e. referenced items all cluster towards the tail of the LRU under memory pressure and the head of the LRU contains the reclaimable objects.
So I think the correct solution is to use
LRU_ROTATEcorrectly rather than try to manage the LRU list order externally like this.Thanks for looking, Dave. Ok, fair enough.
I grafted the LRU list stuff on after I did the original set, and I think the way I designed the refcounting doesn't really work very well with it. It has been a while since I added that in, but I do remember struggling a bit with lock inversion problems trying to do it the more standard way. It's solvable with a
nfsd_filespinlock, but I wanted to avoid that -- still maybe it's the best way.
Quoted 8 lines
What I don't quite get conceptually is how the
list_lrustuff really works...Looking at the dcache's usage,
dentry_lru_addis only called from dput and only removed from the list when you're shrinking the dcache or from__dentry_kill. It will rotate entries to the end of the list viaLRU_ROTATEfrom the shrinker callback ifDCACHE_REFERENCEDwas set, but I don't see how you end up with stuff at the end of the list otherwise.
The LRU lists are managed lazily to keep overhead down. You add them to the list the first time the object becomes unreferenced, and then don't remove it until the object is reclaimed.
This means that when you do repeated "lookup, grab first reference, drop last reference" operations on an object, there is no LRU list management overhead. YOu don't touch the list, you don't touch the locks, etc. All you touch is the referenced flag in the object and when memory pressure occurs the object will then be rotated.
Quoted 16 lines
So, the dcache's LRU list doesn't really seem to keep the entries in LRU order at all. It just prunes a number of entries that haven't been used since the last time the shrinker callback was called, and the rest end up staying on the list in whatever order they were originally added. So...
dentry1 dentry2
allocated
dput
allocated
dputfound
dput again
(maybe many more times)
Quoted 5 lines
Now, the shrinker runs once and skips both because
DCACHE_REFERENCEDis set. It then runs again later and prunes dentry1 before dentry2 even though it has been used many more times since dentry2 has.Am I missing something in how this works?
Yes - the frame of reference. When you look at individual cases like this, it's only "roughly LRU". However, when you scale it up this small "inaccuracy" turns into noise. Put a thousand entries on the LRU, and these two inodes don't get reclaimed until 998 others are reclaimed. Whether d1 or d2 gets reclaimed first really doesn't matter.
Also, the list_lru code needs to scale to tens of millions of objects in the LRU and turning over hundreds of thousands of objects every second, so little inaccuracies really don't matter at this level - performance and scalability are much more important.
Further, the list_lru is not a true global LRU list at all. It's a segmented LRU, with separate LRUs for each node or memcg in the machine. So the LRU really isn't a global LRU at all, it's a bunch of isolated LRUs designed to allow the mm/ subsystem to do NUMA and memcg aware object reclaim...
Combine this all and it becomes obvious why the shrinker is responsible for maintainer LRU order. That comes from object having a "referenced flag" in it to tell the shrinker that since it has seen this object the last time, the object has been referenced again. The shrinker can then remove the referenced flag and rotate the object to the tail of the list.
If sustained memory pressure occurs, then object will eventually make it's way back to the head of the LRU, at which time the shrinker will check the referenced flag again. If it's not set, it gets reclaimed, if it is set, it gets rotated again.
IOWs, the LRU frame of reference is *memory pressure* - the amount of object rotation is determined by the amount of memory pressure. It doesn't matter how many times the code accesses the object, it's whether it is accessed frequently enough during periods of memory pressure that it constantly gets rotated to the tail of the LRU. This basically means the objects that are kept under sustained heavy memory pressure are the objects that are being constantly referenced. Anything that is not regularly referenced will filter to the head of the LRU and hence get reclaimed.
Some subsystems are a bit more complex with their reference "flags". e.g. the XFS buffer cache keeps a "reclaim count" rather than a reference flag that determine the number of times an object will be rotated without an active reference before being reclaimed. This is done becuase no all buffers are equal e.g. btree roots are much more important than interior tree nodes which are more important than leaf nodes, and you can't express this with a single "reference flag". Hence in terms of reclaim count, root > node > leaf and so we hold on to metadata that is more likely to be referenced under sustained memory pressure...
So, it you were expecting a "perfect LRU" list mechanism, the list_lru abstraction isn't it. When looked at from a macro level it gives solid, scalable LRU cache reclaim with NUMA and memcg awareness. When looked at from a micro level, it will display all sorts of quirks that are a result of the design decisions to enable performance, scalability and reclaim features at the macro level...
Cheers,
Dave.
Signature · 6 lines
Dave Chinner [email protected] -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v5 2/20 fs: have flush_delayed_fput flush the workqueue job
In reply to Jeff LaytonI think there's a potential race in flush_delayed_fput. A kthread does an fput() and that file gets added to the list and the delayed work is scheduled. More than 1 jiffy passes, and the workqueue thread picks up the work and starts running it. Then the kthread calls flush_delayed_work. It sees that the list is empty and returns immediately, even though the __fput for its file may not have run yet.
Close this by making flush_delayed_fput use flush_delayed_work instead, which should immediately schedule the work to run if it's not already, and block until the workqueue job completes.
--- fs/file_table.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/file_table.c +3 -3
@@ -244,6 +244,8 @@ static void ____fput(struct callback_head *work) __fput(container_of(work, struct file, f_u.fu_rcuhead)); } +static DECLARE_DELAYED_WORK(delayed_fput_work, delayed_fput); +/* * If kernel thread really needs to have the final fput() it has done * to complete, call this. The only user right now is the boot - we
@@ -256,11 +258,9 @@ static void ____fput(struct callback_head *work)*/ void flush_delayed_fput (void ) { -delayed_fput (NULL ); +flush_delayed_work (&delayed_fput_work); } -static DECLARE_DELAYED_WORK(delayed_fput_work, delayed_fput); -void fput (struct file *file) {if (atomic_long_dec_and_test (&file->f_count)) {
Signature · 1 line
2.4.3
PATCH v5 3/20 fs: add a kerneldoc header to fput
In reply to Jeff Layton...and move its EXPORT_SYMBOL just below the function.
--- fs/file_table.c | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-)
fs/file_table.c +20 -1
@@ -261,6 +261,25 @@ void flush_delayed_fput(void)flush_delayed_work (&delayed_fput_work); } +/** +* fput - put a struct file reference +* @file: file of which to put the reference +* +* This function decrements the reference count for the struct file reference, +* and queues it up for destruction if the count goes to zero. In the case of +* most tasks we queue it to the task_work infrastructure, which will be run +* just before the task returns back to userspace. kthreads however never +* return to userspace, so for those we add them to a global list and schedule +* a delayed workqueue job to do the final cleanup work. +* +* Why not just do it synchronously? __fput can involve taking locks of all +* sorts, and doing it synchronously means that the callers must take extra care +* not to deadlock. That can be very difficult to ensure, so by deferring it +* until just before return to userland or to the workqueue, we sidestep that +* nastiness. Also, __fput can be quite stack intensive, so doing a final fput +* has the possibility of blowing up if we don't take steps to ensure that we +* have enough stack space to make it work. +*/ void fput (struct file *file) {if (atomic_long_dec_and_test (&file->f_count)) {
@@ -281,6 +300,7 @@ void fput(struct file *file)schedule_delayed_work (&delayed_fput_work,1 ); } } +EXPORT_SYMBOL (fput);/* * synchronous analog of fput(); for kernel threads that might be needed
@@ -299,7 +319,6 @@ void __fput_sync(struct file *file) } } -EXPORT_SYMBOL (fput);void put_filp (struct file *file) {
Signature · 1 line
2.4.3
PATCH v5 4/20 fs: add fput_queue
In reply to Jeff LaytonWhen nfsd caches a file, we want to be able to close it down in advance of setlease attempts. Setting a lease is generally done at the behest of userland, so we need a mechanism to ensure that a userland task can completely close a file without having to return back to userspace.
To do this, we borrow the delayed_fput infrastructure that kthreads use. fput_queue will queue to the delayed_fput list if the last reference was put. The caller can then call flush_delayed_fput to ensure that the files are completely closed before proceeding.
--- fs/file_table.c | 27 +++++++++++++++++++++++++++ include/linux/file.h | 1 + 2 files changed, 28 insertions(+)
fs/file_table.c +27 -0
@@ -302,6 +302,33 @@ void fput(struct file *file) }EXPORT_SYMBOL (fput); +/** +* fput_queue - do an fput without using task_work +* @file: file of which to put the reference +* +* When fput is called in the context of a userland process, it'll queue the +* actual work (__fput()) to be done just before returning to userland. In some +* cases however, we need to ensure that the __fput runs before that point. +* There is no safe way to flush work that has been queued via task_work_add +* however, so to do this we borrow the delayed_fput infrastructure that +* kthreads use. The userland process can use fput_queue() on one or more +* struct files and then call flush_delayed_fput() to ensure that they are +* completely closed before proceeding. +* +* Returns true if the final fput was done, false otherwise. The caller can +* use this to determine whether to flush_delayed_fput afterward. +*/ +bool fput_queue (struct file *file) +{ +if (atomic_long_dec_and_test (&file->f_count)) { +if (llist_add (&file->f_u.fu_llist, &delayed_fput_list)) +schedule_delayed_work (&delayed_fput_work,1 ); +return true; + } +return false; +} +EXPORT_SYMBOL (fput_queue); +/* * synchronous analog of fput(); for kernel threads that might be needed * in some umount() (and thus can't use flush_delayed_fput() without
include/linux/file.h +1 -0
@@ -12,6 +12,7 @@struct file ;extern void fput (struct file *); +extern bool fput_queue (struct file *);struct file_operations ;struct vfsmount ;
Signature · 1 line
2.4.3
PATCH v5 7/20 locks: create a new notifier chain for lease attempts
In reply to Jeff LaytonWith the new file caching infrastructure in nfsd, we can end up holding files open for an indefinite period of time, even when they are still idle. This may prevent the kernel from handing out leases on the file, which is something we don't want to block.
Fix this by running a SRCU notifier call chain whenever on any lease attempt. nfsd can then purge the cache for that inode before returning.
Since SRCU is only conditionally compiled in, we must only define the new chain if it's enabled, and users of the chain must ensure that SRCU is enabled.
--- fs/locks.c | 37 +++++++++++++++++++++++++++++++++++++ include/linux/fs.h | 1 + 2 files changed, 38 insertions(+)
fs/locks.c +37 -0
@@ -166,6 +166,7 @@ int lease_break_time = 45;DEFINE_STATIC_LGLOCK (file_lock_lglock); static DEFINE_PER_CPU(struct hlist_head, file_lock_list); +/* * The blocked_hash is used to find POSIX lock loops for deadlock detection. * It is protected by blocked_lock_lock.
@@ -1780,6 +1781,40 @@ int generic_setlease(struct file *filp, long arg, struct file_lock **flp, }EXPORT_SYMBOL (generic_setlease); +#if IS_ENABLED (CONFIG_SRCU ) +/* +* Kernel subsystems can register to be notified on any attempt to set +* a new lease with the lease_notifier_chain. This is used by (e.g.) nfsd +* to close files that it may have cached when there is an attempt to set a +* conflicting lease. +*/ +struct srcu_notifier_head lease_notifier_chain; +EXPORT_SYMBOL_GPL (lease_notifier_chain); + +static inline void +lease_notifier_chain_init (void ) +{ +srcu_init_notifier_head (&lease_notifier_chain); +} + +static inline void +setlease_notifier (long arg,struct file_lock *lease) +{ +if (arg !=F_UNLCK ) +srcu_notifier_call_chain (&lease_notifier_chain, arg, lease); +} +#else /* !IS_ENABLED(CONFIG_SRCU) */ +static inline void +lease_notifier_chain_init (void ) +{ +} + +static inline void +setlease_notifier (long arg,struct file_lock *lease) +{ +} +#endif /* IS_ENABLED(CONFIG_SRCU) */ +/** * vfs_setlease - sets a lease on an open file * @filp: file pointer
@@ -1800,6 +1835,7 @@ EXPORT_SYMBOL(generic_setlease);int vfs_setlease (struct file *filp,long arg,struct file_lock **lease,void **priv) { +setlease_notifier (arg, *lease);if (filp->f_op->setlease)return filp->f_op->setlease (filp, arg, lease, priv);else
@@ -2696,6 +2732,7 @@ static int __init filelock_init(void)for_each_possible_cpu (i)INIT_HLIST_HEAD (per_cpu_ptr (&file_lock_list, i)); +lease_notifier_chain_init ();return 0 ; }
include/linux/fs.h +1 -0
@@ -1042,6 +1042,7 @@ extern int fcntl_setlease(unsigned int fd, struct file *filp, long arg);extern int fcntl_getlease (struct file *filp);/* fs/locks.c */ +extern struct srcu_notifier_head lease_notifier_chain;void locks_free_lock_context (struct file_lock_context *ctx);void locks_free_lock (struct file_lock *fl);extern void locks_init_lock (struct file_lock *);
Signature · 1 line
2.4.3
PATCH v5 9/20 sunrpc: add a new cache_detail operation for when a cache is flushed
In reply to Jeff LaytonWhen the exports table is changed, exportfs will usually write a new time to the "flush" file in the nfsd.export cache procfile. This tells the kernel to flush any entries that are older than that value.
This gives us a mechanism to tell whether an unexport might have occurred. Add a new ->flush cache_detail operation that is called after flushing the cache whenever someone writes to a "flush" file.
--- include/linux/sunrpc/cache.h | 1 + net/sunrpc/cache.c | 3 +++ 2 files changed, 4 insertions(+)
include/linux/sunrpc/cache.h +1 -0
@@ -98,6 +98,7 @@ struct cache_detail { int has_died);struct cache_head * (*alloc)(void ); +void (*flush)(void );int (*match)(struct cache_head *orig,struct cache_head *new);void (*init)(struct cache_head *orig,struct cache_head *new);void (*update)(struct cache_head *orig,struct cache_head *new);
net/sunrpc/cache.c +3 -0
@@ -1451,6 +1451,9 @@ static ssize_t write_flush(struct file *file, const char __user *buf, cd->nextcheck =seconds_since_boot ();cache_flush (); +if (cd->flush) + cd->flush (); + *ppos += count;return count; }
Signature · 1 line
2.4.3
PATCH v5 10/20 nfsd: add a new struct file caching facility to nfsd
In reply to Jeff LaytonCurrently, NFSv2/3 reads and writes have to open a file, do the read or write and then close it again for each RPC. This is highly inefficient, especially when the underlying filesystem has a relatively slow open routine.
This patch adds a new open file cache to knfsd. Rather than doing an open for each RPC, the read/write handlers can call into this cache to see if there is one already there for the correct filehandle and NFS_MAY_READ/WRITE flags.
If there isn't an entry, then we create a new one and attempt to perform the open. If there is, then we wait until the entry is fully instantiated and return it if it is at the end of the wait. If it's not, then we attempt to take over construction.
Since the main goal is to speed up NFSv2/3 I/O, we don't want to close these files on last put of these objects. We need to keep them around for a little while since we never know when the next READ/WRITE will come in.
Note that this patch just adds the infrastructure to allow the caching of open files. Later patches will actually make nfsd use it.
--- fs/nfsd/Kconfig | 2 + fs/nfsd/Makefile | 3 +- fs/nfsd/export.c | 14 ++ fs/nfsd/filecache.c | 573 ++++++++++++++++++++++++++++++++++++++++++++++++++++ fs/nfsd/filecache.h | 37 ++++ fs/nfsd/nfssvc.c | 10 +- fs/nfsd/trace.h | 127 ++++++++++++ fs/nfsd/vfs.c | 3 +- fs/nfsd/vfs.h | 1 + 9 files changed, 767 insertions(+), 3 deletions(-) create mode 100644 fs/nfsd/filecache.c create mode 100644 fs/nfsd/filecache.h
fs/nfsd/Kconfig +2 -0
@@ -6,6 +6,8 @@ config NFSD select SUNRPC select EXPORTFS select NFS_ACL_SUPPORT if NFSD_V2_ACL + select SRCU + select FSNOTIFY depends on MULTIUSER help Choose Y here if you want to allow other computers to access
fs/nfsd/Makefile +2 -1
@@ -10,7 +10,8 @@ obj-$(CONFIG_NFSD) += nfsd.o nfsd-y += trace.o nfsd-y += nfssvc.o nfsctl.o nfsproc.o nfsfh.o vfs.o \ - export.o auth.o lockd.o nfscache.o nfsxdr.o stats.o + export.o auth.o lockd.o nfscache.o nfsxdr.o \ + stats.o filecache.o nfsd-$(CONFIG_NFSD_FAULT_INJECTION) += fault_inject.o nfsd-$(CONFIG_NFSD_V2_ACL) += nfs2acl.o nfsd-$(CONFIG_NFSD_V3) += nfs3proc.o nfs3xdr.o
fs/nfsd/export.c +14 -0
@@ -21,6 +21,7 @@#include "nfsfh.h" #include "netns.h" #include "pnfs.h" +#include "filecache.h" #define NFSDDBG_FACILITY NFSDDBG_EXPORT
@@ -231,6 +232,18 @@ static struct cache_head *expkey_alloc(void)return NULL ; } +static void +expkey_flush (void ) +{ +/* +* Take the nfsd_mutex here to ensure that the file cache is not +* destroyed while we're in the middle of flushing. +*/ +mutex_lock (&nfsd_mutex); +nfsd_file_cache_purge (); +mutex_unlock (&nfsd_mutex); +} +static struct cache_detail svc_expkey_cache_template = { .owner =THIS_MODULE , .hash_size =EXPKEY_HASHMAX ,
@@ -243,6 +256,7 @@ static struct cache_detail svc_expkey_cache_template = { .init = expkey_init, .update = expkey_update, .alloc = expkey_alloc, + .flush = expkey_flush, }; static int
fs/nfsd/filecache.c new file +573 -0
573 lines not on this page · raw message
fs/nfsd/filecache.h new file +37 -0
@@ -0,0 +1,37 @@ +#ifndef _FS_NFSD_FILECACHE_H +#define _FS_NFSD_FILECACHE_H + +#include <linux/fsnotify_backend.h> + +/* +* A representation of a file that has been opened by knfsd. These are hashed +* in the hashtable by inode pointer value. Note that this object doesn't +* hold a reference to the inode by itself, so the nf_inode pointer should +* never be dereferenced, only be used for comparison. +*/ +struct nfsd_file { +struct hlist_node nf_node; +struct list_head nf_lru; +struct rcu_head nf_rcu; +struct file *nf_file; +#define NFSD_FILE_HASHED (0) +#define NFSD_FILE_PENDING (1) +#define NFSD_FILE_BREAK_READ (2) +#define NFSD_FILE_BREAK_WRITE (3) +unsigned long nf_flags; +struct inode *nf_inode; +unsigned int nf_hashval; +atomic_t nf_ref; +unsigned char nf_may; +struct fsnotify_mark nf_mark; +}; + +int nfsd_file_cache_init (void ); +void nfsd_file_cache_purge (void ); +void nfsd_file_cache_shutdown (void ); +void nfsd_file_put (struct nfsd_file *nf); +struct nfsd_file *nfsd_file_get (struct nfsd_file *nf); +void nfsd_file_close_inode_sync (struct inode *inode); +__be32 nfsd_file_acquire (struct svc_rqst *rqstp,struct svc_fh *fhp, +unsigned int may_flags,struct nfsd_file **nfp); +#endif /* _FS_NFSD_FILECACHE_H */
fs/nfsd/nfssvc.c +9 -1
@@ -22,6 +22,7 @@#include "cache.h" #include "vfs.h" #include "netns.h" +#include "filecache.h" #define NFSDDBG_FACILITY NFSDDBG_SVC
@@ -224,11 +225,17 @@ static int nfsd_startup_generic(int nrservs)if (ret) goto dec_users; - ret =nfs4_state_start (); + ret =nfsd_file_cache_init ();if (ret) goto out_racache; + + ret =nfs4_state_start (); +if (ret) + goto out_file_cache;return 0 ; +out_file_cache: +nfsd_file_cache_shutdown (); out_racache:nfsd_racache_shutdown (); dec_users:
@@ -242,6 +249,7 @@ static void nfsd_shutdown_generic(void)return ;nfs4_state_shutdown (); +nfsd_file_cache_shutdown ();nfsd_racache_shutdown (); }
fs/nfsd/trace.h +127 -0
139 lines not on this page · raw message
fs/nfsd/vfs.c +2 -1
@@ -623,7 +623,8 @@ nfsd_access(struct svc_rqst *rqstp, struct svc_fh *fhp, u32 *access, u32 *suppor }#endif /* CONFIG_NFSD_V3 */ -static int nfsd_open_break_lease (struct inode *inode,int access) +int +nfsd_open_break_lease (struct inode *inode,int access) {unsigned int mode;
fs/nfsd/vfs.h +1 -0
@@ -69,6 +69,7 @@ __be32 do_nfsd_create(struct svc_rqst *, struct svc_fh *,__be32 nfsd_commit (struct svc_rqst *,struct svc_fh *,loff_t ,unsigned long );#endif /* CONFIG_NFSD_V3 */ +int nfsd_open_break_lease (struct inode *,int );__be32 nfsd_open (struct svc_rqst *,struct svc_fh *,umode_t ,int ,struct file **);struct raparms ;
Signature · 1 line
2.4.3
PATCH v5 11/20 nfsd: keep some rudimentary stats on nfsd_file cache
In reply to Jeff LaytonPer chain count and max length, protected by the per-chain spinlock. When the file is read, we walk the array of buckets and fetch the count from each.
--- fs/nfsd/filecache.c | 40 ++++++++++++++++++++++++++++++++++++++++ fs/nfsd/filecache.h | 1 + fs/nfsd/nfsctl.c | 10 ++++++++++ 3 files changed, 51 insertions(+)
fs/nfsd/filecache.c +40 -0
@@ -11,6 +11,7 @@#include <linux/sched.h> #include <linux/list_lru.h> #include <linux/fsnotify_backend.h> +#include <linux/seq_file.h> #include "vfs.h" #include "nfsd.h"
@@ -30,6 +31,8 @@struct nfsd_fcache_bucket {struct hlist_head nfb_head;spinlock_t nfb_lock; +unsigned int nfb_count; +unsigned int nfb_maxcount; };static struct kmem_cache *nfsd_file_slab;
@@ -111,6 +114,7 @@ nfsd_file_unhash(struct nfsd_file *nf)trace_nfsd_file_unhash (nf);if (test_bit (NFSD_FILE_HASHED , &nf->nf_flags)) { + --nfsd_file_hashtbl[nf->nf_hashval].nfb_count;clear_bit (NFSD_FILE_HASHED , &nf->nf_flags);hlist_del_rcu (&nf->nf_node);list_lru_del (&nfsd_file_lru, &nf->nf_lru);
@@ -491,6 +495,9 @@ retry:list_lru_add (&nfsd_file_lru, &new->nf_lru);hlist_add_head_rcu (&new->nf_node, &nfsd_file_hashtbl[hashval].nfb_head); + ++nfsd_file_hashtbl[hashval].nfb_count; + nfsd_file_hashtbl[hashval].nfb_maxcount =max (nfsd_file_hashtbl[hashval].nfb_maxcount, + nfsd_file_hashtbl[hashval].nfb_count);spin_unlock (&nfsd_file_hashtbl[hashval].nfb_lock);/* This should never fail since we set allow_dups to true */
@@ -571,3 +578,36 @@ open_file:wake_up_bit (&nf->nf_flags,NFSD_FILE_PENDING ); goto out; } + +/* +* Note that fields may be added, removed or reordered in the future. Programs +* scraping this file for info should test the labels to ensure they're +* getting the correct field. +*/ +static int nfsd_file_cache_stats_show (struct seq_file *m,void *v) +{ +unsigned int i, count =0 , longest =0 ; + +/* +* No need for spinlocks here since we're not terribly interested in +* accuracy. We do take the nfsd_mutex simply to ensure that we +* don't end up racing with server shutdown +*/ +mutex_lock (&nfsd_mutex); +if (nfsd_file_hashtbl) { +for (i =0 ; i <NFSD_FILE_HASH_SIZE ; i++) { + count += nfsd_file_hashtbl[i].nfb_count; + longest =max (longest, nfsd_file_hashtbl[i].nfb_count); + } + } +mutex_unlock (&nfsd_mutex); + +seq_printf (m,"total entries: %u\n" , count); +seq_printf (m,"longest chain: %u\n" , longest); +return 0 ; +} + +int nfsd_file_cache_stats_open (struct inode *inode,struct file *file) +{ +return single_open (file, nfsd_file_cache_stats_show,NULL ); +}
fs/nfsd/filecache.h +1 -0
@@ -34,4 +34,5 @@ struct nfsd_file *nfsd_file_get(struct nfsd_file *nf);void nfsd_file_close_inode_sync (struct inode *inode);__be32 nfsd_file_acquire (struct svc_rqst *rqstp,struct svc_fh *fhp,unsigned int may_flags,struct nfsd_file **nfp); +int nfsd_file_cache_stats_open (struct inode *,struct file *);#endif /* _FS_NFSD_FILECACHE_H */
fs/nfsd/nfsctl.c +10 -0
@@ -22,6 +22,7 @@#include "state.h" #include "netns.h" #include "pnfs.h" +#include "filecache.h" /* * We have a single directory with several nodes in it.
@@ -36,6 +37,7 @@ enum { NFSD_Threads, NFSD_Pool_Threads, NFSD_Pool_Stats, + NFSD_File_Cache_Stats, NFSD_Reply_Cache_Stats, NFSD_Versions, NFSD_Ports,
@@ -220,6 +222,13 @@ static const struct file_operations pool_stats_operations = { .owner = THIS_MODULE, }; +static struct file_operations file_cache_stats_operations = { + .open = nfsd_file_cache_stats_open, + .read = seq_read, + .llseek = seq_lseek, + .release = single_release, +}; +static struct file_operations reply_cache_stats_operations = { .open = nfsd_reply_cache_stats_open, .read = seq_read,
@@ -1138,6 +1147,7 @@ static int nfsd_fill_super(struct super_block * sb, void * data, int silent) [NFSD_Threads] = {"threads", &transaction_ops, S_IWUSR|S_IRUSR}, [NFSD_Pool_Threads] = {"pool_threads", &transaction_ops, S_IWUSR|S_IRUSR}, [NFSD_Pool_Stats] = {"pool_stats", &pool_stats_operations, S_IRUGO}, + [NFSD_File_Cache_Stats] = {"file_cache_stats", &file_cache_stats_operations, S_IRUGO}, [NFSD_Reply_Cache_Stats] = {"reply_cache_stats", &reply_cache_stats_operations, S_IRUGO}, [NFSD_Versions] = {"versions", &transaction_ops, S_IWUSR|S_IRUSR}, [NFSD_Ports] = {"portlist", &transaction_ops, S_IWUSR|S_IRUGO},
Signature · 1 line
2.4.3
PATCH v5 15/20 nfsd: hook nfsd_commit up to the nfsd_file cache
In reply to Jeff LaytonUse cached filps if possible instead of opening a new one every time.
--- fs/nfsd/vfs.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
fs/nfsd/vfs.c +7 -7
@@ -1055,9 +1055,9 @@ __be32 nfsd_commit(struct svc_rqst *rqstp, struct svc_fh *fhp, loff_t offset, unsigned long count) { - struct file *file; -loff_t end =LLONG_MAX ; -__be32 err = nfserr_inval; + struct nfsd_file *nf; +loff_t end =LLONG_MAX ; +__be32 err = nfserr_inval;if (offset <0 ) goto out;
@@ -1067,12 +1067,12 @@ nfsd_commit(struct svc_rqst *rqstp, struct svc_fh *fhp, goto out; } - err =nfsd_open (rqstp, fhp,S_IFREG , -NFSD_MAY_WRITE |NFSD_MAY_NOT_BREAK_LEASE , &file); + err =nfsd_file_acquire (rqstp, fhp, +NFSD_MAY_WRITE |NFSD_MAY_NOT_BREAK_LEASE , &nf);if (err) goto out;if (EX_ISSYNC (fhp->fh_export)) { -int err2 =vfs_fsync_range (file, offset, end,0 ); +int err2 =vfs_fsync_range (nf->nf_file, offset, end,0 );if (err2 != -EINVAL ) err =nfserrno (err2);
@@ -1080,7 +1080,7 @@ nfsd_commit(struct svc_rqst *rqstp, struct svc_fh *fhp, err = nfserr_notsupp; } -fput (file); +nfsd_file_put (nf); out:return err; }
Signature · 1 line
2.4.3
PATCH v5 16/20 nfsd: convert nfs4_file->fi_fds array to use nfsd_files
In reply to Jeff Layton--- fs/nfsd/nfs4state.c | 23 ++++++++++++----------- fs/nfsd/state.h | 2 +- 2 files changed, 13 insertions(+), 12 deletions(-)
fs/nfsd/nfs4state.c +12 -11
@@ -49,6 +49,7 @@#include "netns.h" #include "pnfs.h" +#include "filecache.h" #define NFSDDBG_FACILITY NFSDDBG_PROC
@@ -292,7 +293,7 @@ static struct file * __nfs4_get_fd(struct nfs4_file *f, int oflag) {if (f->fi_fds[oflag]) -return get_file (f->fi_fds[oflag]); +return get_file (f->fi_fds[oflag]->nf_file);return NULL ; }
@@ -449,17 +450,17 @@ static void __nfs4_file_put_access(struct nfs4_file *fp, int oflag)might_lock (&fp->fi_lock);if (atomic_dec_and_lock (&fp->fi_access[oflag], &fp->fi_lock)) { -struct file *f1 =NULL ; -struct file *f2 =NULL ; +struct nfsd_file *f1 =NULL ; +struct nfsd_file *f2 =NULL ;swap (f1, fp->fi_fds[oflag]);if (atomic_read (&fp->fi_access[1 - oflag]) ==0 )swap (f2, fp->fi_fds[O_RDWR ]);spin_unlock (&fp->fi_lock);if (f1) -fput (f1); +nfsd_file_put (f1);if (f2) -fput (f2); +nfsd_file_put (f2); } }
@@ -3841,7 +3842,7 @@ static __be32 nfs4_get_vfs_file(struct svc_rqst *rqstp, struct nfs4_file *fp, struct svc_fh *cur_fh, struct nfs4_ol_stateid *stp, struct nfsd4_open *open) { - struct file *filp = NULL; + struct nfsd_file *nf = NULL;__be32 status;int oflag =nfs4_access_to_omode (open->op_share_access);int access =nfs4_access_to_access (open->op_share_access);
@@ -3877,18 +3878,18 @@ static __be32 nfs4_get_vfs_file(struct svc_rqst *rqstp, struct nfs4_file *fp,if (!fp->fi_fds[oflag]) {spin_unlock (&fp->fi_lock); - status =nfsd_open (rqstp, cur_fh,S_IFREG , access, &filp); + status =nfsd_file_acquire (rqstp, cur_fh, access, &nf);if (status) goto out_put_access;spin_lock (&fp->fi_lock);if (!fp->fi_fds[oflag]) { - fp->fi_fds[oflag] = filp; - filp =NULL ; + fp->fi_fds[oflag] = nf; + nf =NULL ; } }spin_unlock (&fp->fi_lock); -if (filp) -fput (filp); +if (nf) +nfsd_file_put (nf); status =nfsd4_truncate (rqstp, cur_fh, open);if (status)
fs/nfsd/state.h +1 -1
@@ -491,7 +491,7 @@ struct nfs4_file { };struct list_head fi_clnt_odstate;/* One each for O_RDONLY, O_WRONLY, O_RDWR: */ -struct file * fi_fds[3 ]; +struct nfsd_file *fi_fds[3 ];/* * Each open or lock stateid contributes 0-4 to the counts * below depending on which bits are set in st_access_bitmap:
Signature · 1 line
2.4.3
PATCH v5 17/20 nfsd: have nfsd_test_lock use the nfsd_file cache
In reply to Jeff Layton--- fs/nfsd/nfs4state.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
fs/nfsd/nfs4state.c +4 -4
@@ -5596,11 +5596,11 @@ out:*/ static __be32 nfsd_test_lock (struct svc_rqst *rqstp,struct svc_fh *fhp,struct file_lock *lock) { -struct file *file; -__be32 err =nfsd_open (rqstp, fhp,S_IFREG ,NFSD_MAY_READ , &file); +struct nfsd_file *nf; +__be32 err =nfsd_file_acquire (rqstp, fhp,NFSD_MAY_READ , &nf);if (!err) { - err =nfserrno (vfs_test_lock (file, lock)); -fput (file); + err =nfserrno (vfs_test_lock (nf->nf_file, lock)); +nfsd_file_put (nf); }return err; }
Signature · 1 line
2.4.3
PATCH v5 19/20 nfsd: hook up nfs4_preprocess_stateid_op to the nfsd_file cache
In reply to Jeff LaytonHave nfs4_preprocess_stateid_op pass back a nfsd_file instead of a filp. Since we now presume that the struct file will be persistent in most cases, we can stop fiddling with the raparms in the read code. This also means that we don't really care about the rd_tmp_file field anymore.
--- fs/nfsd/nfs4proc.c | 32 ++++++++++++++++---------------- fs/nfsd/nfs4state.c | 24 ++++++++++-------------- fs/nfsd/nfs4xdr.c | 16 +++++----------- fs/nfsd/state.h | 2 +- fs/nfsd/xdr4.h | 15 +++++++-------- 5 files changed, 39 insertions(+), 50 deletions(-)
fs/nfsd/nfs4proc.c +16 -16
@@ -758,7 +758,7 @@ nfsd4_read(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, {__be32 status; - read->rd_filp =NULL ; + read->rd_nf =NULL ;if (read->rd_offset >=OFFSET_MAX )return nfserr_inval;
@@ -775,7 +775,7 @@ nfsd4_read(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,/* check stateid */ status =nfs4_preprocess_stateid_op (rqstp, cstate, &read->rd_stateid, -RD_STATE , &read->rd_filp, &read->rd_tmp_file); +RD_STATE , &read->rd_nf);if (status) {dprintk ("NFSD: nfsd4_read: couldn't process stateid!\n" ); goto out;
@@ -921,7 +921,7 @@ nfsd4_setattr(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,if (setattr->sa_iattr.ia_valid &ATTR_SIZE ) { status =nfs4_preprocess_stateid_op (rqstp, cstate, - &setattr->sa_stateid,WR_STATE ,NULL ,NULL ); + &setattr->sa_stateid,WR_STATE ,NULL );if (status) {dprintk ("NFSD: nfsd4_setattr: couldn't process stateid!\n" );return status;
@@ -977,7 +977,7 @@ nfsd4_write(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, struct nfsd4_write *write) {stateid_t *stateid = &write->wr_stateid; -struct file *filp =NULL ; +struct nfsd_file *nf =NULL ;__be32 status = nfs_ok;unsigned long cnt;int nvecs;
@@ -986,7 +986,7 @@ nfsd4_write(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,return nfserr_inval; status =nfs4_preprocess_stateid_op (rqstp, cstate, stateid,WR_STATE , - &filp,NULL ); + &nf);if (status) {dprintk ("NFSD: nfsd4_write: couldn't process stateid!\n" );return status;
@@ -999,10 +999,10 @@ nfsd4_write(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, nvecs =fill_in_write_vector (rqstp->rq_vec, write);WARN_ON_ONCE (nvecs >ARRAY_SIZE (rqstp->rq_vec)); - status =nfsd_vfs_write (rqstp, &cstate->current_fh, filp, + status =nfsd_vfs_write (rqstp, &cstate->current_fh, nf->nf_file, write->wr_offset, rqstp->rq_vec, nvecs, &cnt, &write->wr_how_written); -fput (filp); +nfsd_file_put (nf); write->wr_bytes_written = cnt;
@@ -1014,21 +1014,21 @@ nfsd4_fallocate(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, struct nfsd4_fallocate *fallocate, int flags) {__be32 status = nfserr_notsupp; -struct file *file; +struct nfsd_file *nf; status =nfs4_preprocess_stateid_op (rqstp, cstate, &fallocate->falloc_stateid, -WR_STATE , &file,NULL ); +WR_STATE , &nf);if (status != nfs_ok) {dprintk ("NFSD: nfsd4_fallocate: couldn't process stateid!\n" );return status; } - status =nfsd4_vfs_fallocate (rqstp, &cstate->current_fh, file, + status =nfsd4_vfs_fallocate (rqstp, &cstate->current_fh, nf->nf_file, fallocate->falloc_offset, fallocate->falloc_length, flags); -fput (file); +nfsd_file_put (nf);return status; }
@@ -1053,11 +1053,11 @@ nfsd4_seek(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, {int whence;__be32 status; -struct file *file; +struct nfsd_file *nf; status =nfs4_preprocess_stateid_op (rqstp, cstate, &seek->seek_stateid, -RD_STATE , &file,NULL ); +RD_STATE , &nf);if (status) {dprintk ("NFSD: nfsd4_seek: couldn't process stateid!\n" );return status;
@@ -1079,14 +1079,14 @@ nfsd4_seek(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,* Note: This call does change file->f_pos, but nothing in NFSD * should ever file->f_pos. */ - seek->seek_pos =vfs_llseek (file, seek->seek_offset, whence); + seek->seek_pos =vfs_llseek (nf->nf_file, seek->seek_offset, whence);if (seek->seek_pos <0 ) status =nfserrno (seek->seek_pos); -else if (seek->seek_pos >=i_size_read (file_inode (file))) +else if (seek->seek_pos >=i_size_read (file_inode (nf->nf_file))) seek->seek_eof = true; out: -fput (file); +nfsd_file_put (nf);return status; }
fs/nfsd/nfs4state.c +10 -14
@@ -4658,7 +4658,7 @@ nfs4_check_olstateid(struct svc_fh *fhp, struct nfs4_ol_stateid *ols, int flags)static __be32 nfs4_check_file (struct svc_rqst *rqstp,struct svc_fh *fhp,struct nfs4_stid *s, -struct file **filpp,bool *tmp_file,int flags) +struct nfsd_file **nfp,int flags) {int acc = (flags &RD_STATE ) ?NFSD_MAY_READ :NFSD_MAY_WRITE ;struct nfsd_file *nf;
@@ -4668,20 +4668,18 @@ nfs4_check_file(struct svc_rqst *rqstp, struct svc_fh *fhp, struct nfs4_stid *s,if (nf) { status =nfsd_permission (rqstp, fhp->fh_export, fhp->fh_dentry, acc |NFSD_MAY_OWNER_OVERRIDE ); -if (status) +if (status) { +nfsd_file_put (nf); goto out; + } }else { status =nfsd_file_acquire (rqstp, fhp, acc, &nf);if (status)return status; - -if (tmp_file) - *tmp_file = true; } - *filpp =get_file (nf->nf_file); + *nfp = nf; out: -nfsd_file_put (nf);return status; }
@@ -4691,7 +4689,7 @@ out:__be32 nfs4_preprocess_stateid_op (struct svc_rqst *rqstp,struct nfsd4_compound_state *cstate,stateid_t *stateid, -int flags,struct file **filpp,bool *tmp_file) +int flags,struct nfsd_file **nfp) {struct svc_fh *fhp = &cstate->current_fh;struct inode *ino =d_inode (fhp->fh_dentry);
@@ -4700,10 +4698,8 @@ nfs4_preprocess_stateid_op(struct svc_rqst *rqstp,struct nfs4_stid *s =NULL ;__be32 status; -if (filpp) - *filpp =NULL ; -if (tmp_file) - *tmp_file = false; +if (nfp) + *nfp =NULL ;if (grace_disallows_io (net, ino))return nfserr_grace;
@@ -4740,8 +4736,8 @@ nfs4_preprocess_stateid_op(struct svc_rqst *rqstp, status =nfs4_check_fh (fhp, s); done: -if (!status && filpp) - status =nfs4_check_file (rqstp, fhp, s, filpp, tmp_file, flags); +if (status == nfs_ok && nfp) + status =nfs4_check_file (rqstp, fhp, s, nfp, flags); out:if (s)nfs4_put_stid (s);
fs/nfsd/nfs4xdr.c +5 -11
@@ -49,6 +49,7 @@#include "cache.h" #include "netns.h" #include "pnfs.h" +#include "filecache.h" #ifdef CONFIG_NFSD_V4_SECURITY_LABEL #include <linux/security.h>
@@ -3460,14 +3461,14 @@ nfsd4_encode_read(struct nfsd4_compoundres *resp, __be32 nfserr, {unsigned long maxcount;struct xdr_stream *xdr = &resp->xdr; -struct file *file = read->rd_filp; +struct file *file;int starting_len = xdr->buf->len; -struct raparms *ra =NULL ;__be32 *p;if (nfserr) goto out; + file = read->rd_nf->nf_file; p =xdr_reserve_space (xdr,8 );/* eof flag and byte count */ if (!p) {WARN_ON_ONCE (test_bit (RQ_SPLICE_OK , &resp->rqstp->rq_flags));
@@ -3487,24 +3488,17 @@ nfsd4_encode_read(struct nfsd4_compoundres *resp, __be32 nfserr, (xdr->buf->buflen - xdr->buf->len)); maxcount = min_t(unsigned long, maxcount, read->rd_length); -if (read->rd_tmp_file) - ra =nfsd_init_raparms (file); -if (file->f_op->splice_read &&test_bit (RQ_SPLICE_OK , &resp->rqstp->rq_flags)) nfserr =nfsd4_encode_splice_read (resp, read, file, maxcount);else nfserr =nfsd4_encode_readv (resp, read, file, maxcount); -if (ra) -nfsd_put_raparams (file, ra); -if (nfserr)xdr_truncate_encode (xdr, starting_len); - out: -if (file) -fput (file); +if (read->rd_nf) +nfsd_file_put (read->rd_nf);return nfserr; }
fs/nfsd/state.h +1 -1
@@ -579,7 +579,7 @@ struct nfsd_net;extern __be32 nfs4_preprocess_stateid_op (struct svc_rqst *rqstp,struct nfsd4_compound_state *cstate,stateid_t *stateid, -int flags,struct file **filp,bool *tmp_file); +int flags,struct nfsd_file **filp);__be32 nfsd4_lookup_stateid (struct nfsd4_compound_state *cstate,stateid_t *stateid,unsigned char typemask,struct nfs4_stid **s,struct nfsd_net *nn);
fs/nfsd/xdr4.h +7 -8
@@ -268,15 +268,14 @@ struct nfsd4_open_downgrade {struct nfsd4_read { -stateid_t rd_stateid;/* request */ -u64 rd_offset;/* request */ -u32 rd_length;/* request */ -int rd_vlen; -struct file *rd_filp; -bool rd_tmp_file; +stateid_t rd_stateid;/* request */ +u64 rd_offset;/* request */ +u32 rd_length;/* request */ +int rd_vlen; +struct nfsd_file *rd_nf; -struct svc_rqst *rd_rqstp;/* response */ -struct svc_fh * rd_fhp;/* response */ +struct svc_rqst *rd_rqstp;/* response */ +struct svc_fh *rd_fhp;/* response */ };struct nfsd4_readdir {
Signature · 1 line
2.4.3
PATCH v5 20/20 nfsd: rip out the raparms cache
In reply to Jeff LaytonNothing uses it anymore.
--- fs/nfsd/nfssvc.c | 14 +----- fs/nfsd/vfs.c | 147 ------------------------------------------------------- fs/nfsd/vfs.h | 6 --- 3 files changed, 1 insertion(+), 166 deletions(-)
fs/nfsd/nfssvc.c +1 -13
@@ -216,18 +216,9 @@ static int nfsd_startup_generic(int nrservs)if (nfsd_users++)return 0 ; -/* -* Readahead param cache - will no-op if it already exists. -* (Note therefore results will be suboptimal if number of -* threads is modified after nfsd start.) -*/ - ret =nfsd_racache_init (2 *nrservs); -if (ret) - goto dec_users; - ret =nfsd_file_cache_init ();if (ret) - goto out_racache; + goto dec_users; ret =nfs4_state_start ();if (ret)
@@ -236,8 +227,6 @@ static int nfsd_startup_generic(int nrservs) out_file_cache:nfsd_file_cache_shutdown (); -out_racache: -nfsd_racache_shutdown (); dec_users: nfsd_users--;return ret;
@@ -250,7 +239,6 @@ static void nfsd_shutdown_generic(void)nfs4_state_shutdown ();nfsd_file_cache_shutdown (); -nfsd_racache_shutdown (); }static bool nfsd_needs_lockd (void )
fs/nfsd/vfs.c +0 -147
162 lines not on this page · raw message
fs/nfsd/vfs.h +0 -6
@@ -39,8 +39,6 @@typedef int (*nfsd_filldir_t )(void *,const char *,int ,loff_t ,u64 ,unsigned );/* nfsd/vfs.c */ -int nfsd_racache_init (int ); -void nfsd_racache_shutdown (void );int nfsd_cross_mnt (struct svc_rqst *rqstp,struct dentry **dpp,struct svc_export **expp); __be32 nfsd_lookup(struct svc_rqst *, struct svc_fh *,
@@ -74,7 +72,6 @@ __be32 nfsd_open(struct svc_rqst *, struct svc_fh *, umode_t, int, struct file **);__be32 nfsd_open_verified (struct svc_rqst *,struct svc_fh *,umode_t ,int ,struct file **); -struct raparms ;__be32 nfsd_splice_read (struct svc_rqst *,struct file *,loff_t ,unsigned long *); __be32 nfsd_readv(struct file *, loff_t, struct kvec *, int,
@@ -107,9 +104,6 @@ __be32 nfsd_statfs(struct svc_rqst *, struct svc_fh *,__be32 nfsd_permission (struct svc_rqst *,struct svc_export *,struct dentry *,int ); -struct raparms *nfsd_init_raparms (struct file *file); -void nfsd_put_raparams (struct file *file,struct raparms *ra); -static inline int fh_want_write (struct svc_fh *fh) {int ret =mnt_want_write (fh->fh_export->ex_path.mnt);
Signature · 1 line
2.4.3