linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: mgorman@techsingularity.net
Cc: linux-nfs@vger.kernel.org, linux-mm@kvack.org, kuba@kernel.org
Subject: [PATCH v2 0/4] Reduce page allocator traffic caused by NFSD
Date: Mon, 22 Feb 2021 10:23:00 -0500	[thread overview]
Message-ID: <161400722731.195066.9584156841718557193.stgit@klimt.1015granger.net> (raw)

Hi Mel-

I've been testing these four, which include a working version of
your bulk allocator patch. In "Refresh rq_pages" I've replaced
the cond_resched() call with schedule_timeout(), as you requested.

As always, review comments and test results are welcome.

---

Chuck Lever (3):
      SUNRPC: Set rq_page_end differently
      SUNRPC: Refresh rq_pages using a bulk page allocator
      SUNRPC: Cache pages that were replaced during a read splice

Mel Gorman (1):
      mm: alloc_pages_bulk()


 fs/nfsd/vfs.c                   |   4 +-
 include/linux/gfp.h             |  24 +++++++
 include/linux/sunrpc/svc.h      |   1 +
 include/linux/sunrpc/svc_xprt.h |  28 ++++++++
 mm/page_alloc.c                 | 110 +++++++++++++++++++++++++++++++-
 net/sunrpc/svc.c                |   7 ++
 net/sunrpc/svc_xprt.c           |  55 ++++++++++++----
 7 files changed, 214 insertions(+), 15 deletions(-)

--
Chuck Lever



             reply	other threads:[~2021-02-22 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 15:23 Chuck Lever [this message]
2021-02-22 15:23 ` [PATCH v2 1/4] SUNRPC: Set rq_page_end differently Chuck Lever
2021-02-22 15:23 ` [PATCH v2 2/4] mm: alloc_pages_bulk() Chuck Lever
2021-02-22 15:23 ` [PATCH v2 3/4] SUNRPC: Refresh rq_pages using a bulk page allocator Chuck Lever
2021-02-22 17:37   ` kernel test robot
2021-02-22 17:49   ` kernel test robot
2021-02-22 15:23 ` [PATCH v2 4/4] SUNRPC: Cache pages that were replaced during a read splice Chuck Lever
2021-02-26  7:19   ` NeilBrown
2021-02-26 14:13     ` Chuck Lever

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=161400722731.195066.9584156841718557193.stgit@klimt.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=kuba@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    /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;
as well as URLs for NNTP newsgroup(s).