From: 王贇 <yun.wang@linux.alibaba.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.ibm.com>
Subject: Re: [PATCH v2 1/3] sched/numa: advanced per-cgroup numa statistic
Date: Fri, 29 Nov 2019 13:19:33 +0800
Message-ID: <f9da5ce8-519e-62b4-36f7-8e5bbf0485fd@linux.alibaba.com> (raw)
In-Reply-To: <b97ce489-c5c5-0670-a553-0e45d593de2c@linux.alibaba.com>
On 2019/11/29 上午9:52, 王贇 wrote:
[snip]
>> That would avoid the partitioning question completely, exposed values
>> would be simple numbers and provided information should be equal. A
>> drawback is that such a sampling would be slower (but sufficient for the
>> illustrating example).
>
> You mean the cgroup numa stat just give the accumulated local/remote access?
>
> As long as the counter won't overflow, maybe... sounds easier to explain too.
>
> So user tracing locality will then get just one percentage (calculated on
> their own) from a cgroup, but one should be enough to represent the situation.
>
> Sounds like a good idea to me :-) will try to do that in next version.
I did some research regarding cpuacct, and find cpuacct_charge() is a good
place to do hierarchical update, however, what we get there is the execution
time delta since last update_curr().
I'm afraid we can't just do local/remote accumulation since the sample period
now is changing, still have to accumulate the execution time into locality
regions.
While at least we should be able to address your concern regarding exectime
collection :-)
Regards,
Michael Wang
>
> Regards,
> Michael Wang
>
>>
>> Michal
>>
next prev parent reply index
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 3:43 [PATCH 0/3] sched/numa: introduce advanced " 王贇
2019-11-13 3:44 ` [PATCH 1/3] sched/numa: advanced per-cgroup " 王贇
2019-11-13 3:45 ` [PATCH 2/3] sched/numa: expose per-task pages-migration-failure 王贇
2019-11-13 3:45 ` [PATCH 3/3] sched/numa: documentation for per-cgroup numa stat 王贇
2019-11-13 15:09 ` Jonathan Corbet
2019-11-14 1:52 ` 王贇
2019-11-13 18:28 ` Iurii Zaikin
2019-11-14 2:22 ` 王贇
2019-11-15 2:29 ` [PATCH v2 " 王贇
2019-11-20 9:45 ` [PATCH 0/3] sched/numa: introduce advanced numa statistic 王贇
2019-11-25 1:35 ` 王贇
2019-11-27 1:48 ` [PATCH v2 " 王贇
2019-11-27 1:49 ` [PATCH v2 1/3] sched/numa: advanced per-cgroup " 王贇
2019-11-27 10:19 ` Mel Gorman
2019-11-28 2:09 ` 王贇
2019-11-28 12:39 ` Michal Koutný
2019-11-28 13:41 ` 王贇
2019-11-28 15:58 ` Michal Koutný
2019-11-29 1:52 ` 王贇
2019-11-29 5:19 ` 王贇 [this message]
2019-11-29 10:06 ` Michal Koutný
2019-12-02 2:11 ` 王贇
2019-11-27 1:50 ` [PATCH v2 2/3] sched/numa: expose per-task pages-migration-failure 王贇
2019-11-27 10:00 ` Mel Gorman
2019-12-02 2:22 ` 王贇
2019-11-27 1:50 ` [PATCH v2 3/3] sched/numa: documentation for per-cgroup numa stat 王贇
2019-11-27 4:58 ` Randy Dunlap
2019-11-27 5:54 ` 王贇
2019-12-03 5:59 ` [PATCH v3 0/2] sched/numa: introduce numa locality 王贇
2019-12-03 6:00 ` [PATCH v3 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-04 2:33 ` Randy Dunlap
2019-12-04 2:38 ` 王贇
2019-12-03 6:02 ` [PATCH v3 2/2] sched/numa: documentation for per-cgroup numa statistics 王贇
2019-12-03 13:43 ` Jonathan Corbet
2019-12-04 2:27 ` 王贇
2019-12-04 7:58 ` [PATCH v4 0/2] sched/numa: introduce numa locality 王贇
2019-12-04 7:59 ` [PATCH v4 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-05 3:28 ` Randy Dunlap
2019-12-05 3:29 ` Randy Dunlap
2019-12-05 3:52 ` 王贇
2019-12-04 8:00 ` [PATCH v4 2/2] sched/numa: documentation for per-cgroup numa statistics 王贇
2019-12-05 3:40 ` Randy Dunlap
2019-12-05 6:53 ` [PATCH v5 0/2] sched/numa: introduce numa locality 王贇
2019-12-05 6:53 ` [PATCH v5 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-05 6:54 ` [PATCH v5 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2019-12-10 2:19 ` [PATCH v5 0/2] sched/numa: introduce numa locality 王贇
2019-12-13 1:43 ` [PATCH v6 " 王贇
2019-12-13 1:47 ` [PATCH v6 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-03 15:14 ` Michal Koutný
2020-01-04 4:51 ` 王贇
2019-12-13 1:48 ` [PATCH v6 2/2] sched/numa: documentation for per-cgroup numa 王贇
2019-12-27 2:22 ` [PATCH v6 0/2] sched/numa: introduce numa locality 王贇
2020-01-17 2:19 ` 王贇
2020-01-19 6:08 ` [PATCH v7 " 王贇
2020-01-19 6:09 ` [PATCH v7 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-19 6:09 ` [PATCH v7 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2020-01-21 0:12 ` Randy Dunlap
2020-01-21 1:58 ` 王贇
2020-01-21 1:56 ` [PATCH v8 0/2] sched/numa: introduce numa locality 王贇
2020-01-21 1:57 ` [PATCH v8 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-21 1:57 ` [PATCH v8 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2020-01-21 2:08 ` Randy Dunlap
Reply instructions:
You may reply publically 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=f9da5ce8-519e-62b4-36f7-8e5bbf0485fd@linux.alibaba.com \
--to=yun.wang@linux.alibaba.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=yzaikin@google.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
Linux-Fsdevel Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \
linux-fsdevel@vger.kernel.org
public-inbox-index linux-fsdevel
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git