From: Chuck Lever <chuck.lever@oracle.com>
To: NeilBrown <neilb@suse.de>
Cc: Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/2 v2] nfsd: fully close files in the nfsd threads
Date: Fri, 15 Dec 2023 10:52:26 -0500 [thread overview]
Message-ID: <ZXx2Oklp51L+fIXp@tissot.1015granger.net> (raw)
In-Reply-To: <20231215012059.30857-1-neilb@suse.de>
On Fri, Dec 15, 2023 at 12:18:29PM +1100, NeilBrown wrote:
> This is a revised version of my recent series to have nfs close files
> directly and not leave work to an async work queue.
>
> This version takes a more cautious approach and only using __fput_sync()
> where there is a reasonable case that it could make a practical
> difference.
Hi Neil, thanks for the revisions and documentation.
Jeff and I would like to see this set spend some time in linux-next
before getting merged. We're just about on the cusp of closing out
nfsd-next for v6.8, so my plan is to apply these to nfsd-next just
as soon as v6.9 opens to give testers and bots plenty of time to
exercise them.
--
Chuck Lever
prev parent reply other threads:[~2023-12-15 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 1:18 [PATCH 0/2 v2] nfsd: fully close files in the nfsd threads NeilBrown
2023-12-15 1:18 ` [PATCH 1/2] nfsd: Don't leave work of closing files to a work queue NeilBrown
2023-12-15 1:18 ` [PATCH 2/2] nfsd: use __fput_sync() to avoid delayed closing of files NeilBrown
2023-12-15 8:27 ` [PATCH 3/2 SQUASH] " NeilBrown
2023-12-15 11:02 ` Jeff Layton
2023-12-15 11:01 ` [PATCH 0/2 v2] nfsd: fully close files in the nfsd threads Jeff Layton
2023-12-15 15:52 ` Chuck Lever [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=ZXx2Oklp51L+fIXp@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.com \
/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