From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, willy@infradead.org
Subject: Re: [PATCH] mm/page_alloc: remove prefetchw() on freeing page to buddy system
Date: Tue, 2 Jul 2024 08:57:57 +0200 [thread overview]
Message-ID: <fdfc990b-0191-49c8-9d12-9f44ad5444d6@redhat.com> (raw)
In-Reply-To: <20240702020931.7061-1-richard.weiyang@gmail.com>
On 02.07.24 04:09, Wei Yang wrote:
> The prefetchw() is introduced from an ancient patch[1].
>
> The change log says:
>
> The basic idea is to free higher order pages instead of going
> through every single one. Also, some unnecessary atomic operations
> are done away with and replaced with non-atomic equivalents, and
> prefetching is done where it helps the most. For a more in-depth
> discusion of this patch, please see the linux-ia64 archives (topic
> is "free bootmem feedback patch").
>
> So there are several changes improve the bootmem freeing, in which the
> most basic idea is freeing higher order pages. And as Matthew says,
> "Itanium CPUs of this era had no prefetchers."
>
> I did 10 round bootup tests before and after this change, the data
> doesn't prove prefetchw() help speeding up bootmem freeing. The sum of
> the 10 round bootmem freeing time after prefetchw() removal even 5.2%
> faster than before.
I suspect this is noise, though.
>
> [1]: https://lore.kernel.org/linux-ia64/40F46962.4090604@sgi.com/
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> Suggested-by: Matthew Wilcox <willy@infradead.org>
> CC: David Hildenbrand <david@redhat.com>
>
> ---
> The patch is based on mm-stable with David's change.
> ---
> mm/page_alloc.c | 13 ++-----------
> 1 file changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 116ee33fd1ce..c46aedfc9a12 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1236,16 +1236,11 @@ void __meminit __free_pages_core(struct page *page, unsigned int order,
> */
> if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG) &&
> unlikely(context == MEMINIT_HOTPLUG)) {
> - prefetchw(p);
> - for (loop = 0; loop < (nr_pages - 1); loop++, p++) {
> - prefetchw(p + 1);
> + for (loop = 0; loop < nr_pages; loop++, p++) {
> VM_WARN_ON_ONCE(PageReserved(p));
> __ClearPageOffline(p);
> set_page_count(p, 0);
> }
Something like:
for (;;) {
...
if (++loop >= nr_pages)
break;
p++;
}
Might generate slightly better code, because we know that we execute the
loop body at least once. We use that in set_ptes(), for example.
> - VM_WARN_ON_ONCE(PageReserved(p));
> - __ClearPageOffline(p);
> - set_page_count(p, 0);
>
> /*
> * Freeing the page with debug_pagealloc enabled will try to
> @@ -1255,14 +1250,10 @@ void __meminit __free_pages_core(struct page *page, unsigned int order,
> debug_pagealloc_map_pages(page, nr_pages);
> adjust_managed_page_count(page, nr_pages);
> } else {
> - prefetchw(p);
> - for (loop = 0; loop < (nr_pages - 1); loop++, p++) {
> - prefetchw(p + 1);
> + for (loop = 0; loop < nr_pages; loop++, p++) {
> __ClearPageReserved(p);
> set_page_count(p, 0);
> }
> - __ClearPageReserved(p);
> - set_page_count(p, 0);
>
> /* memblock adjusts totalram_pages() manually. */
> atomic_long_add(nr_pages, &page_zone(page)->managed_pages);
Much better
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-02 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 2:09 [PATCH] mm/page_alloc: remove prefetchw() on freeing page to buddy system Wei Yang
2024-07-02 6:22 ` Andrew Morton
2024-07-03 0:01 ` Wei Yang
2024-07-03 0:49 ` Andrew Morton
2024-07-03 0:55 ` Wei Yang
2024-07-02 6:57 ` David Hildenbrand [this message]
2024-07-03 0:12 ` Wei Yang
2024-07-03 8:40 ` David Hildenbrand
2024-07-04 3:30 ` Matthew Wilcox
2024-07-04 3:37 ` Andrew Morton
2024-07-04 3:39 ` Matthew Wilcox
2024-07-04 3:43 ` Andrew Morton
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=fdfc990b-0191-49c8-9d12-9f44ad5444d6@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).