From: "Michal Koutný" <mkoutny@suse.com>
To: "Chen, Yu C" <yu.c.chen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Tim Chen <tim.c.chen@intel.com>, Aubrey Li <aubrey.li@intel.com>,
Rik van Riel <riel@surriel.com>,
Raghavendra K T <raghavendra.kt@amd.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Xunlei Pang <xlpang@linux.alibaba.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, Chen Yu <yu.chen.surf@foxmail.com>
Subject: Re: [PATCH] sched/numa: Add statistics of numa balance task migration and swap
Date: Thu, 3 Apr 2025 20:03:01 +0200 [thread overview]
Message-ID: <ufnmsikyh6budl4qkhy5o4m76yldvlns3yja743bdwvxwsljer@ztbsqf7gx6oi> (raw)
In-Reply-To: <7cbbbd8f-a4b4-491d-bb60-97defff6007c@intel.com>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Thu, Apr 03, 2025 at 10:47:44AM +0800, "Chen, Yu C" <yu.c.chen@intel.com> wrote:
> In the context of NUMA balancing, it would be helpful to not only monitor on
> the activities of individual task/thread but also the resource usage and
> task migrations at the group level - which helps us quickly evaluate the
> performance and resource usage of the container - like per memcg
> numa_pages_migrated, numa_pte_updates introduced in
Somehow I thought that these are the useful metrics (amount of misplaced
memory) and the aggregated task stats aren't interesting (they'd be more
or less proportion of total number of tasks in the group and you don't
know which task it was).
> Got it, will do in next version.
OK.
Thanks,
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-03 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 1:06 Chen Yu
2025-04-02 13:24 ` Michal Koutný
2025-04-02 17:43 ` K Prateek Nayak
2025-04-03 17:57 ` Michal Koutný
2025-04-03 2:47 ` Chen, Yu C
2025-04-03 18:03 ` Michal Koutný [this message]
2025-04-02 13:33 ` Madadi Vineeth Reddy
2025-04-02 17:23 ` K Prateek Nayak
2025-04-02 18:08 ` Madadi Vineeth Reddy
2025-04-02 17:35 ` K Prateek Nayak
2025-04-03 2:49 ` Chen, Yu C
2025-04-02 18:50 ` Madadi Vineeth Reddy
2025-04-03 2:52 ` Chen, Yu C
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=ufnmsikyh6budl4qkhy5o4m76yldvlns3yja743bdwvxwsljer@ztbsqf7gx6oi \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=muchun.song@linux.dev \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tim.c.chen@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=xlpang@linux.alibaba.com \
--cc=yu.c.chen@intel.com \
--cc=yu.chen.surf@foxmail.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