From: Matthew Wilcox <willy@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "mgorman@suse.de" <mgorman@suse.de>,
"brouer@redhat.com" <brouer@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Fwd: alloc_pages_bulk()
Date: Tue, 9 Feb 2021 22:01:27 +0000 [thread overview]
Message-ID: <20210209220127.GB308988@casper.infradead.org> (raw)
In-Reply-To: <EEB0B974-6E63-41A0-9C01-F0DEA39FC4BF@oracle.com>
On Mon, Feb 08, 2021 at 05:50:51PM +0000, Chuck Lever wrote:
> > We've been discussing how NFSD can more efficiently refill its
> > receive buffers (currently alloc_page() in a loop; see
> > net/sunrpc/svc_xprt.c::svc_alloc_arg()).
I'm not familiar with the sunrpc architecture, but this feels like you're
trying to optimise something that shouldn't exist. Ideally a write
would ask the page cache for the pages that correspond to the portion
of the file which is being written to. I appreciate that doesn't work
well for, eg, NFS-over-TCP, but for NFS over any kind of RDMA, that
should be possible, right?
next prev parent reply other threads:[~2021-02-09 22:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2A0C36E7-8CB0-486F-A8DB-463CA28C5C5D@oracle.com>
2021-02-08 17:50 ` Fwd: alloc_pages_bulk() Chuck Lever
2021-02-09 10:31 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-09 13:37 ` alloc_pages_bulk() Chuck Lever
2021-02-09 17:27 ` alloc_pages_bulk() Vlastimil Babka
2021-02-10 9:51 ` alloc_pages_bulk() Christoph Hellwig
2021-02-10 8:41 ` alloc_pages_bulk() Mel Gorman
2021-02-10 11:41 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-10 13:07 ` alloc_pages_bulk() Mel Gorman
2021-02-10 22:58 ` alloc_pages_bulk() Chuck Lever
2021-02-11 9:12 ` alloc_pages_bulk() Mel Gorman
2021-02-11 12:26 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-15 12:00 ` alloc_pages_bulk() Mel Gorman
2021-02-15 16:10 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-22 9:42 ` alloc_pages_bulk() Mel Gorman
2021-02-22 11:42 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-22 14:08 ` alloc_pages_bulk() Mel Gorman
2021-02-11 16:20 ` alloc_pages_bulk() Chuck Lever
2021-02-15 12:06 ` alloc_pages_bulk() Mel Gorman
2021-02-15 16:00 ` alloc_pages_bulk() Chuck Lever
2021-02-22 20:44 ` alloc_pages_bulk() Jesper Dangaard Brouer
2021-02-09 22:01 ` Matthew Wilcox [this message]
2021-02-09 22:55 ` alloc_pages_bulk() 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=20210209220127.GB308988@casper.infradead.org \
--to=willy@infradead.org \
--cc=brouer@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mgorman@suse.de \
/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).