From: "NeilBrown" <neilb@suse.de>
To: "Chuck Lever" <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] Bulk-release pages during NFSD read splice
Date: Fri, 09 Jul 2021 09:23:10 +1000 [thread overview]
Message-ID: <162578659050.31036.16278478540386858207@noble.neil.brown.name> (raw)
In-Reply-To: <162575623717.2532.8517369487503961860.stgit@klimt.1015granger.net>
On Fri, 09 Jul 2021, Chuck Lever wrote:
>
> In this version of the series, each nfsd thread never accrues more
> than 16 pages. We can easily make that larger or smaller, but 16
> already reduces the rate of put_pages() calls to a minute fraction
> of what it was, and does not consume much additional space in struct
> svc_rqst.
>
> Comments welcome!
Very nice. Does "1/16" really count as "minute"? Or did I miss
something and it is actually a smaller fraction?
Either way: excellent work.
Reviewed-by: NeilBrown <neilb@suse.de>
NeilBrown
>
> ---
>
> Chuck Lever (3):
> NFSD: Clean up splice actor
> SUNRPC: Add svc_rqst_replace_page() API
> NFSD: Batch release pages during splice read
>
>
> fs/nfsd/vfs.c | 20 +++++---------------
> include/linux/sunrpc/svc.h | 5 +++++
> net/sunrpc/svc.c | 29 +++++++++++++++++++++++++++++
> 3 files changed, 39 insertions(+), 15 deletions(-)
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2021-07-08 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 15:26 Chuck Lever
2021-07-08 15:26 ` [PATCH v3 1/3] NFSD: Clean up splice actor Chuck Lever
2021-07-08 15:26 ` [PATCH v3 2/3] SUNRPC: Add svc_rqst_replace_page() API Chuck Lever
2021-07-08 23:30 ` Matthew Wilcox
2021-07-09 3:04 ` Chuck Lever III
2021-07-08 15:26 ` [PATCH v3 3/3] NFSD: Batch release pages during splice read Chuck Lever
2021-07-08 23:23 ` NeilBrown [this message]
2021-07-09 2:58 ` [PATCH v3 0/3] Bulk-release pages during NFSD read splice Chuck Lever III
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=162578659050.31036.16278478540386858207@noble.neil.brown.name \
--to=neilb@suse.de \
--cc=chuck.lever@oracle.com \
--cc=linux-mm@kvack.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