[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d67d273c-41e7-d046-cdd1-0b2faae2ed07@linux.alibaba.com>
Date: Tue, 3 Dec 2019 17:25:49 +0800
From: 王贇 <yun.wang@...ux.alibaba.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Michal Koutný <mkoutny@...e.com>,
Mel Gorman <mgorman@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND] sched/numa: expose per-task
pages-migration-failure
On 2019/12/3 下午3:16, Ingo Molnar wrote:
[snip]
>> kernel/sched/debug.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c
>> index f7e4579e746c..73c4809c8f37 100644
>> --- a/kernel/sched/debug.c
>> +++ b/kernel/sched/debug.c
>> @@ -848,6 +848,7 @@ static void sched_show_numa(struct task_struct *p, struct seq_file *m)
>> P(total_numa_faults);
>> SEQ_printf(m, "current_node=%d, numa_group_id=%d\n",
>> task_node(p), task_numa_group_id(p));
>> + SEQ_printf(m, "migfailed=%lu\n", p->numa_faults_locality[2]);
>
> Any reason not to expose the other 2 fields of this array as well, which
> show remote/local migrations?
The rest are local/remote faults counter, AFAIK not related to
migration, when the CPU triggered PF is from the same node of page
(before migration), local faults increased.
Regards,
Michael Wang
>
> Thanks,
>
> Ingo
>
Powered by blists - more mailing lists