From: Vlastimil Babka <vbabka@suse.cz>
To: Jesper Dangaard Brouer <brouer@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>
Cc: "mgorman@suse.de" <mgorman@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: alloc_pages_bulk()
Date: Tue, 9 Feb 2021 18:27:11 +0100 [thread overview]
Message-ID: <7e8efe19-94da-3f75-2380-2a54b36d5ab5@suse.cz> (raw)
In-Reply-To: <20210209113108.1ca16cfa@carbon>
On 2/9/21 11:31 AM, Jesper Dangaard Brouer wrote:
> On Mon, 8 Feb 2021 17:50:51 +0000
> Chuck Lever <chuck.lever@oracle.com> wrote:
>
>> Sorry for resending. I misremembered the linux-mm address.
>>
>> > Begin forwarded message:
>> >
>> > [ please Cc: me, I'm not subscribed to linux-mm ]
>> >
>> > 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()).
>> >
>
> It looks like you could also take advantage of bulk free in:
> svc_free_res_pages()
>
> I would like to use the page bulk alloc API here:
> https://github.com/torvalds/linux/blob/master/net/core/page_pool.c#L201-L209
>
>
>> > Neil Brown pointed me to this old thread:
>> >
>> > https://lore.kernel.org/lkml/20170109163518.6001-1-mgorman@techsingularity.net/
>> >
>> > We see that many of the prerequisites are in v5.11-rc, but
>> > alloc_page_bulk() is not. I tried forward-porting 4/4 in that
>> > series, but enough internal APIs have changed since 2017 that
>> > the patch does not come close to applying and compiling.
>
> I forgot that this was never merged. It is sad as Mel showed huge
> improvement with his work.
>
>> > I'm wondering:
>> >
>> > a) is there a newer version of that work?
>> >
>
> Mel, why was this work never merged upstream?
Hmm the cover letter of that work says:
> The fourth patch introduces a bulk page allocator with no
> in-kernel users as an example for Jesper and others who want to
> build a page allocator for DMA-coherent pages. It hopefully is
> relatively easy to modify this API and the one core function toget > the
semantics they require.
So it seems there were no immediate users to finalize the API?
>> > b) if not, does there exist a preferred API in 5.11 for bulk
>> > page allocation?
>> >
>> > Many thanks for any guidance!
>
> I have a kernel module that micro-bench the API alloc_pages_bulk() here:
> https://github.com/netoptimizer/prototype-kernel/blob/master/kernel/mm/bench/page_bench04_bulk.c#L97
>
next prev parent reply other threads:[~2021-02-09 17:43 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 ` Vlastimil Babka [this message]
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 ` Fwd: alloc_pages_bulk() Matthew Wilcox
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=7e8efe19-94da-3f75-2380-2a54b36d5ab5@suse.cz \
--to=vbabka@suse.cz \
--cc=brouer@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mgorman@suse.de \
--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