linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Qi Zheng <zhengqi.arch@bytedance.com>
To: akpm@linux-foundation.org, rppt@kernel.org, david@redhat.com,
	vbabka@suse.cz, mhocko@suse.com
Cc: willy@infradead.org, mgorman@techsingularity.net,
	mingo@kernel.org, aneesh.kumar@linux.ibm.com,
	ying.huang@intel.com, hannes@cmpxchg.org, osalvador@suse.de,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Qi Zheng <zhengqi.arch@bytedance.com>
Subject: [PATCH v2 0/2] handle memoryless nodes more appropriately
Date: Thu, 19 Oct 2023 15:36:25 +0800	[thread overview]
Message-ID: <cover.1697687357.git.zhengqi.arch@bytedance.com> (raw)

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.

This series is based on the next-20231018.

Comments and suggestions are welcome.

Thanks,
Qi

Changlog in v1 -> v2:
 - modify the commit message in [PATCH 1/2], mention that it can also fix the
   specific crash. (suggested by Ingo Molnar)

Qi Zheng (2):
  mm: page_alloc: skip memoryless nodes entirely
  mm: memory_hotplug: drop memoryless node from fallback lists

 mm/memory_hotplug.c | 2 +-
 mm/page_alloc.c     | 7 +++++--
 2 files changed, 6 insertions(+), 3 deletions(-)

-- 
2.30.2



             reply	other threads:[~2023-10-19  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  7:36 Qi Zheng [this message]
2023-10-19  7:36 ` [PATCH v2 1/2] mm: page_alloc: skip memoryless nodes entirely Qi Zheng
2023-10-19  8:07   ` David Hildenbrand
2023-10-19  8:21     ` Qi Zheng
2023-10-19  7:36 ` [PATCH v2 2/2] mm: memory_hotplug: drop memoryless node from fallback lists Qi Zheng
2023-10-19  8:11   ` David Hildenbrand
2023-10-19  8:22     ` Qi Zheng
2023-10-19  7:56 ` [PATCH v2 0/2] handle memoryless nodes more appropriately David Hildenbrand
2023-10-19  8:17   ` 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=cover.1697687357.git.zhengqi.arch@bytedance.com \
    --to=zhengqi.arch@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.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