From: Michal Hocko <mhocko@suse.com>
To: Dongjoo Seo <dongjoo.linux.dev@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dave@stgolabs.net,
dan.j.williams@intel.com, nifan@outlook.com,
a.manzanares@samsung.com
Subject: Re: [PATCH] mm/page_alloc: fix NUMA stats update for cpu-less nodes
Date: Wed, 23 Oct 2024 20:03:24 +0200 [thread overview]
Message-ID: <Zxk6bHlrP5S_0LBK@tiehlicka> (raw)
In-Reply-To: <20241023175037.9125-1-dongjoo.linux.dev@gmail.com>
On Wed 23-10-24 10:50:37, Dongjoo Seo wrote:
> This patch corrects this issue by:
What is this issue? Please describe the problem first, ideally describe
the NUMA topology, workload and what kind of misaccounting happens
(expected values vs. really reported values).
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-10-23 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:50 Dongjoo Seo
2024-10-23 18:03 ` Michal Hocko [this message]
2024-10-23 20:41 ` Andrew Morton
2024-10-23 21:38 ` Michal Hocko
2024-10-23 22:15 ` Dongjoo Seo
2024-10-23 22:23 ` Michal Hocko
2024-10-24 4:54 ` Dongjoo Seo
2024-10-24 8:24 ` Michal Hocko
2024-10-24 18:13 ` Dongjoo Seo
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=Zxk6bHlrP5S_0LBK@tiehlicka \
--to=mhocko@suse.com \
--cc=a.manzanares@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=dongjoo.linux.dev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nifan@outlook.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