From: Andrew Morton <akpm@linux-foundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Alexander Halbuer <halbuer@sra.uni-hannover.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm, page_alloc: batch cma update on pcp buffer refill
Date: Thu, 23 Feb 2023 13:48:17 -0800 [thread overview]
Message-ID: <20230223134817.dc1669b51a9c39850a6f86cb@linux-foundation.org> (raw)
In-Reply-To: <89778da7-74a3-2f2a-1668-afe7b15487dc@suse.cz>
On Tue, 21 Feb 2023 11:27:14 +0100 Vlastimil Babka <vbabka@suse.cz> wrote:
>
> > The tables below compare this patch with the initial one using a
> > parallel allocation benchmark. The used kernel config is based on the default
> > debian config but with CONFIG_INIT_ON_ALLOC_DEFAULT_ON=FALSE and
> > CONFIG_CMA=TRUE. The benchmarks have been performed with the default sanity
> > checks enabled as the patch "mm, page_alloc: reduce page alloc/free sanity
> > checks" [2] was not enabled on my test branch.
> > The given times are average allocation times. The improvement is not
> > significant, but the general trend is visible.
>
> Yeah there's some improvement, but if [2] is accepted, then keeping two
> loops there just for the cma update (as there will be no more checking in
> the second loop) will almost certainly stop being a win. And with the risk
> of inaccuracy you pointed out, on top.
>
> ...
>
> > [2] https://lore.kernel.org/linux-mm/20230216095131.17336-1-vbabka@suse.cz/
I've just added "mm, page_alloc: reduce page alloc/free sanity checks"
to mm-unstable.
next prev parent reply other threads:[~2023-02-23 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 12:05 Alexander Halbuer
2023-02-21 10:27 ` Vlastimil Babka
2023-02-23 21:48 ` Andrew Morton [this message]
2023-03-03 12:52 ` Alexander Halbuer
2023-03-03 13:36 ` Vlastimil Babka
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=20230223134817.dc1669b51a9c39850a6f86cb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=halbuer@sra.uni-hannover.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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