mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, david@redhat.com,
	rppt@kernel.org, willy@infradead.org,
	mgorman@techsingularity.net, osalvador@suse.de,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] handle memoryless nodes more appropriately
Date: Wed, 15 Feb 2023 17:36:58 +0100	[thread overview]
Message-ID: <Y+0KKnN8BU6ky6oP@dhcp22.suse.cz> (raw)
In-Reply-To: <20230215152412.13368-1-zhengqi.arch@bytedance.com>

On Wed 15-02-23 23:24:10, Qi Zheng wrote:
> Hi all,
> 
> Currently, in the process of initialization or offline memory, memoryless
> nodes will still be built into the fallback list of itself or other nodes.
> 
> This is not what we expected, so this patch series removes memoryless
> nodes from the fallback list entirely.
> 
> Comments and suggestions are welcome.

This is a tricky area full of surprises and it is really easy to
introduce new problems. What kind of problem/issue are you trying to
solve/handle by these changes?

-- 
Michal Hocko
SUSE Labs

  parent reply	other threads:[~2023-02-15 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 15:24 Qi Zheng
2023-02-15 15:24 ` [PATCH 1/2] mm: page_alloc: skip memoryless nodes entirely Qi Zheng
2023-02-15 15:24 ` [PATCH 2/2] mm: memory_hotplug: drop memoryless node from fallback lists Qi Zheng
2023-02-15 16:36 ` Michal Hocko [this message]
2023-02-15 23:11   ` [PATCH 0/2] handle memoryless nodes more appropriately Qi Zheng
2023-02-16  7:51     ` Michal Hocko
2023-02-16  8:21       ` Qi Zheng
2023-02-16  8:37         ` Michal Hocko
2023-02-16 10:50           ` Qi Zheng

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=Y+0KKnN8BU6ky6oP@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=zhengqi.arch@bytedance.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

all inboxes | Powered by JetHome®