From: Hugh Dickins <hughd@google.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Eric Dumazet <edumazet@google.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm: do not acquire zone lock in is_free_buddy_page()
Date: Wed, 22 Sep 2021 16:23:41 -0700 (PDT) [thread overview]
Message-ID: <26db20dd-8e18-e68a-adb-adf171d62bf8@google.com> (raw)
In-Reply-To: <20210922152833.4023972-1-eric.dumazet@gmail.com>
On Wed, 22 Sep 2021, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Grabbing zone lock in is_free_buddy_page() gives a wrong sense of safety,
> and has potential performance implications when zone is experiencing
> lock contention.
>
> In any case, if a caller needs a stable result, it should grab zone
> lock before calling this function.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Hugh Dickins <hughd@google.com>
Yes indeed, and you have already explained it well above: thanks.
Acked-by: Hugh Dickins <hughd@google.com>
> ---
> mm/page_alloc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index e115e21524739341d409b28379942241ed403060..cd8a72372b047e55c4cde80fe6b7a428d7721027 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -9354,21 +9354,21 @@ void __offline_isolated_pages(unsigned long start_pfn, unsigned long end_pfn)
> }
> #endif
>
> +/*
> + * This function returns a stable result only if called under zone lock.
> + */
> bool is_free_buddy_page(struct page *page)
> {
> - struct zone *zone = page_zone(page);
> unsigned long pfn = page_to_pfn(page);
> - unsigned long flags;
> unsigned int order;
>
> - spin_lock_irqsave(&zone->lock, flags);
> for (order = 0; order < MAX_ORDER; order++) {
> struct page *page_head = page - (pfn & ((1 << order) - 1));
>
> - if (PageBuddy(page_head) && buddy_order(page_head) >= order)
> + if (PageBuddy(page_head) &&
> + buddy_order_unsafe(page_head) >= order)
> break;
> }
> - spin_unlock_irqrestore(&zone->lock, flags);
>
> return order < MAX_ORDER;
> }
> --
> 2.33.0.464.g1972c5931b-goog
prev parent reply other threads:[~2021-09-22 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:28 Eric Dumazet
2021-09-22 23:23 ` Hugh Dickins [this message]
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=26db20dd-8e18-e68a-adb-adf171d62bf8@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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