linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <edumazet@google.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	 Mel Gorman <mgorman@techsingularity.net>,
	Michal Hocko <mhocko@kernel.org>,
	 Shakeel Butt <shakeelb@google.com>, Wei Xu <weixugc@google.com>,
	 Greg Thelen <gthelen@google.com>,
	Hugh Dickins <hughd@google.com>,
	 David Rientjes <rientjes@google.com>
Subject: Re: [PATCH] mm/page_alloc: call check_new_pages() while zone spinlock is not held
Date: Fri, 4 Mar 2022 08:50:03 -0800	[thread overview]
Message-ID: <CANn89iJOAnSz3h36A_gAoog1xRjkaR=3i1L6iz8C_E6DC8TwUw@mail.gmail.com> (raw)
In-Reply-To: <deae2ce6-8a43-5720-319e-cab25ee3bdb6@suse.cz>

On Fri, Mar 4, 2022 at 12:32 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>
>
> Ah, you found out already. Well maybe it could simply be moved inside the
> loop under the locked section and always done when page != NULL? I mean if
> check_new_pages() fails we just leak the problematic pages anyway so they
> are no longer free to allocate anymore and we should not count them as such.
>

Yes, and I guess that calling __mod_zone_freepage_state() for the page
about to be leaked
is just fine.

This means we can call check_newpages() without holding zone spinlock
or hard irqs being masked.

I will test something like:

diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 3589febc6d31928f850ebe5a4015ddc40e0469f3..1804287c1b792b8aa0e964b17eb002b6b1115258
100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3706,10 +3706,10 @@ struct page *rmqueue(struct zone *preferred_zone,
         * allocate greater than order-1 page units with __GFP_NOFAIL.
         */
        WARN_ON_ONCE((gfp_flags & __GFP_NOFAIL) && (order > 1));
-       spin_lock_irqsave(&zone->lock, flags);

        do {
                page = NULL;
+               spin_lock_irqsave(&zone->lock, flags);
                /*
                 * order-0 request can reach here when the pcplist is skipped
                 * due to non-CMA allocation context. HIGHATOMIC area is
@@ -3721,15 +3721,15 @@ struct page *rmqueue(struct zone *preferred_zone,
                        if (page)
                                trace_mm_page_alloc_zone_locked(page,
order, migratetype);
                }
-               if (!page)
+               if (!page) {
                        page = __rmqueue(zone, order, migratetype, alloc_flags);
-       } while (page && check_new_pages(page, order));
-       if (!page)
-               goto failed;
-
-       __mod_zone_freepage_state(zone, -(1 << order),
-                                 get_pcppage_migratetype(page));
-       spin_unlock_irqrestore(&zone->lock, flags);
+                       if (!page)
+                               goto failed;
+               }
+               __mod_zone_freepage_state(zone, -(1 << order),
+                                         get_pcppage_migratetype(page));
+               spin_unlock_irqrestore(&zone->lock, flags);
+       } while (check_new_pages(page, order));

        __count_zid_vm_events(PGALLOC, page_zonenum(page), 1 << order);
        zone_statistics(preferred_zone, zone, 1);


  reply	other threads:[~2022-03-04 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04  1:59 Eric Dumazet
2022-03-04  2:09 ` Eric Dumazet
2022-03-04  8:32   ` Vlastimil Babka
2022-03-04 16:50     ` Eric Dumazet [this message]
2022-03-04  8:26 ` 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='CANn89iJOAnSz3h36A_gAoog1xRjkaR=3i1L6iz8C_E6DC8TwUw@mail.gmail.com' \
    --to=edumazet@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.dumazet@gmail.com \
    --cc=gthelen@google.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=rientjes@google.com \
    --cc=shakeelb@google.com \
    --cc=vbabka@suse.cz \
    --cc=weixugc@google.com \
    /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