linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: David Hildenbrand <david@redhat.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: compaction: early termination in compact_nodes()
Date: Wed, 21 Feb 2024 14:34:34 -0800	[thread overview]
Message-ID: <20240221143434.5ba9efcf6c4dc534d1f1a9f1@linux-foundation.org> (raw)
In-Reply-To: <aec80774-87b7-4d0e-8425-dd363c9d2f03@huawei.com>

On Sat, 17 Feb 2024 10:55:10 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:

> On 2024/2/12 22:22, David Hildenbrand wrote:
> > On 08.02.24 22:14, Andrew Morton wrote:
> >> On Thu, 8 Feb 2024 10:25:08 +0800 Kefeng Wang 
> >> <wangkefeng.wang@huawei.com> wrote:
> >>
> >>> No need to continue try compact memory if pending fatal signal,
> >>> allow loop termination earlier in compact_nodes().
> >>
> >> Seems sensible, but...  why?  Is there some problem which we can
> >> demonstrate with the existing code?  In other words, does this change
> >> provide any observable benefit under any circumstances?
> > 
> > I'd also be curious why the existing fatal_signal_pending() calls are 
> > insufficient.
> 
> The existing fatal_signal_pending() does make compact_zone() breakout of
> the while loop, but it still enter the next zone/next nid, and some 
> unnecessary functions(eg, lru_add_drain) called, no observable benefit
> from test, it is just found from code inspection when refactor 

Fair enough.  I added the above words to the changelog (this material
should have been communicated in the original!) and I'll plan to move
this change into mm-stable next week unless someone stops me.


  reply	other threads:[~2024-02-21 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  9:58 [PATCH] mm: compaction: refactor compact_node() Kefeng Wang
2024-02-07 23:48 ` Andrew Morton
2024-02-08  2:25 ` [PATCH] mm: compaction: early termination in compact_nodes() Kefeng Wang
2024-02-08 21:14   ` Andrew Morton
2024-02-12 14:22     ` David Hildenbrand
2024-02-17  2:55       ` Kefeng Wang
2024-02-21 22:34         ` Andrew Morton [this message]
2024-02-22 14:36           ` Kefeng Wang

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=20240221143434.5ba9efcf6c4dc534d1f1a9f1@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=wangkefeng.wang@huawei.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