linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Dmitry Ilvokhin <d@ilvokhin.com>,
	Vlastimil Babka <vbabka@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Brendan Jackman <jackmanb@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RESEND PATCH v2 0/8] mm: use spinlock guards for zone lock
Date: Wed, 8 Apr 2026 13:07:15 -0700	[thread overview]
Message-ID: <20260408130715.d6772b9675b0182bac9fe427@linux-foundation.org> (raw)
In-Reply-To: <adaFaMGbndSSMaZn@tiehlicka>

On Wed, 8 Apr 2026 18:42:16 +0200 Michal Hocko <mhocko@suse.com> wrote:

> > Dmitry Ilvokhin (8):
> >   mm: use zone lock guard in reserve_highatomic_pageblock()
> >   mm: use zone lock guard in unset_migratetype_isolate()
> >   mm: use zone lock guard in unreserve_highatomic_pageblock()
> >   mm: use zone lock guard in set_migratetype_isolate()
> >   mm: use zone lock guard in take_page_off_buddy()
> >   mm: use zone lock guard in put_page_back_buddy()
> >   mm: use zone lock guard in free_pcppages_bulk()
> >   mm: use zone lock guard in __offline_isolated_pages()
> > 
> >  mm/page_alloc.c     | 53 ++++++++++++-----------------------
> >  mm/page_isolation.c | 67 +++++++++++++++++++--------------------------
> >  2 files changed, 45 insertions(+), 75 deletions(-)
> 
> I like the resulting code. For the whole series.
> Acked-by: Michal Hocko <mhocko@suse.com>

Thanks.

As I mentioned previously, the outcome here hinges on how the
developers who work on this code feel about using guard().  Most of
them are in hiding at present but that's OK - it's post -rc1 fun.



      reply	other threads:[~2026-04-08 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 13:33 Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 1/8] mm: use zone lock guard in reserve_highatomic_pageblock() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 2/8] mm: use zone lock guard in unset_migratetype_isolate() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 3/8] mm: use zone lock guard in unreserve_highatomic_pageblock() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 4/8] mm: use zone lock guard in set_migratetype_isolate() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 5/8] mm: use zone lock guard in take_page_off_buddy() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 6/8] mm: use zone lock guard in put_page_back_buddy() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 7/8] mm: use zone lock guard in free_pcppages_bulk() Dmitry Ilvokhin
2026-04-08 13:33 ` [RESEND PATCH v2 8/8] mm: use zone lock guard in __offline_isolated_pages() Dmitry Ilvokhin
2026-04-08 16:42 ` [RESEND PATCH v2 0/8] mm: use spinlock guards for zone lock Michal Hocko
2026-04-08 20:07   ` Andrew Morton [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=20260408130715.d6772b9675b0182bac9fe427@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=d@ilvokhin.com \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ziy@nvidia.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