public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/9] A course adjustment, maybe...
Date: Fri, 7 Oct 2022 14:19:54 +0000	[thread overview]
Message-ID: <0392D2DB-B0D3-46BC-BAE9-259A2EEDFD4A@oracle.com> (raw)
In-Reply-To: <3376ba7410b6211899c12872195a97219230823c.camel@kernel.org>



> On Oct 7, 2022, at 9:19 AM, Jeff Layton <jlayton@kernel.org> wrote:
> 
> On Thu, 2022-10-06 at 12:20 -0400, Chuck Lever wrote:
>> I'm proposing this series as the first NFSD-related patchset to go
>> into v6.2 (for-next), though I haven't opened that yet.
>> 
>> For quite some time, we've been encouraged to disable filecache
>> garbage collection for NFSv4 files, and I think I found a surgical
>> way to do just that. That is presented in "NFSD: Add an NFSD_FILE_GC
>> flag to enable nfsd_file garbage collection".
>> 
>> Comments and opinions are welcome.
>> 
>> Changes since RFC:
>> - checking nfs4_files for inode aliases is now done only on hash
>>  insertion
>> - the nfs4_file reference count is now bumped only while the RCU
>>  read lock is held
>> - comments and function names have been revised and clarified
>> 
>> I haven't updated the new @want_gc parameter... jury is still out.
>> 
> 
> It was just a nit I noticed since it looked like it was being used as a
> bool. If you think it needs to be an int, then so be it.

I prefer bool in these applications, but in this case, I think "int"
is the safer choice. Thanks for your review!


>> ---
>> 
>> Chuck Lever (7):
>>      NFSD: Pass the target nfsd_file to nfsd_commit()
>>      NFSD: Revert "NFSD: NFSv4 CLOSE should release an nfsd_file immediately"
>>      NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection
>>      NFSD: Use const pointers as parameters to fh_ helpers.
>>      NFSD: Use rhashtable for managing nfs4_file objects
>>      NFSD: Clean up nfs4_preprocess_stateid_op() call sites
>>      NFSD: Trace delegation revocations
>> 
>> Jeff Layton (2):
>>      nfsd: fix nfsd_file_unhash_and_dispose
>>      nfsd: rework hashtable handling in nfsd_do_file_acquire
>> 
>> 
>> fs/nfsd/filecache.c | 165 +++++++++++++++---------------
>> fs/nfsd/filecache.h |   4 +-
>> fs/nfsd/nfs3proc.c  |  10 +-
>> fs/nfsd/nfs4proc.c  |  42 ++++----
>> fs/nfsd/nfs4state.c | 241 ++++++++++++++++++++++++++++++--------------
>> fs/nfsd/nfsfh.h     |  10 +-
>> fs/nfsd/state.h     |   5 +-
>> fs/nfsd/trace.h     |  58 ++++++++++-
>> fs/nfsd/vfs.c       |  19 ++--
>> fs/nfsd/vfs.h       |   3 +-
>> 10 files changed, 351 insertions(+), 206 deletions(-)
> 
> 
> I been doing some testing with this and it seems to be working well. You
> can add:
> 
> Tested-by: Jeff Layton <jlayton@kernel.org>

--
Chuck Lever




      reply	other threads:[~2022-10-07 14:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 16:20 [PATCH v2 0/9] A course adjustment, maybe Chuck Lever
2022-10-06 16:20 ` [PATCH v2 1/9] nfsd: fix nfsd_file_unhash_and_dispose Chuck Lever
2022-10-06 16:20 ` [PATCH v2 2/9] nfsd: rework hashtable handling in nfsd_do_file_acquire Chuck Lever
2022-10-06 16:20 ` [PATCH v2 3/9] NFSD: Pass the target nfsd_file to nfsd_commit() Chuck Lever
2022-10-06 16:20 ` [PATCH v2 4/9] NFSD: Revert "NFSD: NFSv4 CLOSE should release an nfsd_file immediately" Chuck Lever
2022-10-06 16:20 ` [PATCH v2 5/9] NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection Chuck Lever
2022-10-10 23:50   ` NeilBrown
2022-10-11 13:03     ` Chuck Lever III
2022-10-06 16:20 ` [PATCH v2 6/9] NFSD: Use const pointers as parameters to fh_ helpers Chuck Lever
2022-10-06 16:20 ` [PATCH v2 7/9] NFSD: Use rhashtable for managing nfs4_file objects Chuck Lever
2022-10-11  0:16   ` NeilBrown
2022-10-11 12:56     ` Chuck Lever III
2022-10-11 23:37       ` NeilBrown
2022-10-12 15:01         ` Chuck Lever III
2022-10-12 21:18           ` NeilBrown
2022-10-13 14:19             ` Chuck Lever III
2022-10-13 22:14               ` NeilBrown
2022-10-14 12:48                 ` Chuck Lever III
2022-10-12  6:45       ` NeilBrown
2022-10-06 16:20 ` [PATCH v2 8/9] NFSD: Clean up nfs4_preprocess_stateid_op() call sites Chuck Lever
2022-10-06 16:21 ` [PATCH v2 9/9] NFSD: Trace delegation revocations Chuck Lever
2022-10-07 13:19 ` [PATCH v2 0/9] A course adjustment, maybe Jeff Layton
2022-10-07 14:19   ` Chuck Lever III [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0392D2DB-B0D3-46BC-BAE9-259A2EEDFD4A@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox