From: Calum Mackay <calum.mackay@oracle.com>
To: Chuck Lever <cel@kernel.org>,
linux-nfs@vger.kernel.org, linux-mm@kvack.org
Cc: Calum Mackay <calum.mackay@oracle.com>
Subject: Re: [PATCH v1 0/4] NFSD memory allocation optimizations
Date: Sat, 15 Apr 2023 18:24:17 +0100 [thread overview]
Message-ID: <054d240a-f4b4-5c7a-2476-e80edbfd8c61@oracle.com> (raw)
In-Reply-To: <168151777579.1588.7882383278745556830.stgit@klimt.1015granger.net>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
On 15/04/2023 1:17 am, Chuck Lever wrote:
> I've found a few ways to optimize the release of pages in NFSD.
> Please let me know if I'm abusing the release_pages() and pagevec
> APIs.
>
> ---
>
> Chuck Lever (4):
> SUNRPC: Relocate svc_free_res_pages()
> SUNRPC: Convert svc_xprt_release() to the release_pages() API
> SUNRPC: Convert svc_tcp_restore_pages() to the release_pages() API
> SUNRPC: Be even lazier about releasing pages
>
>
> include/linux/sunrpc/svc.h | 12 +-----------
> net/sunrpc/svc.c | 21 +++++++++++++++++++++
> net/sunrpc/svc_xprt.c | 5 +----
> net/sunrpc/svcsock.c | 12 ++++++------
> 4 files changed, 29 insertions(+), 21 deletions(-)
>
> --
> Chuck Lever
>
Looks good to me, Chuck.
Reviewed-by: Calum Mackay <calum.mackay@oracle.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-04-15 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 0:17 Chuck Lever
2023-04-15 0:17 ` [PATCH v1 1/4] SUNRPC: Relocate svc_free_res_pages() Chuck Lever
2023-04-15 0:18 ` [PATCH v1 2/4] SUNRPC: Convert svc_xprt_release() to the release_pages() API Chuck Lever
2023-04-15 0:18 ` [PATCH v1 3/4] SUNRPC: Convert svc_tcp_restore_pages() " Chuck Lever
2023-04-15 0:18 ` [PATCH v1 4/4] SUNRPC: Be even lazier about releasing pages Chuck Lever
2023-04-15 17:24 ` Calum Mackay [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=054d240a-f4b4-5c7a-2476-e80edbfd8c61@oracle.com \
--to=calum.mackay@oracle.com \
--cc=cel@kernel.org \
--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