From: Peter Zijlstra <peterz@infradead.org>
To: Marian Marinov <mm@yuhu.biz>
Cc: lxc-devel@lists.linuxcontainers.org, cgroups@vger.kernel.org,
"Daniel P. Berrange" <berrange@redhat.com>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
Li Zefan <lizefan@huawei.com>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: RFC: cgroups aware proc
Date: Mon, 13 Jan 2014 18:12:38 +0100 [thread overview]
Message-ID: <20140113171238.GS31570@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <52D41316.5080508@yuhu.biz>
On Mon, Jan 13, 2014 at 06:23:50PM +0200, Marian Marinov wrote:
> Hello Peter,
>
> I need help with the scheduler.
>
> I'm currently trying to patch the /proc/loadavg to show the load that is
> only related to the processes from the current cgroup.
>
> I looked trough the code and I was hoping that tsk->sched_task_group->cfs_rq
> struct will give me the needed information, but unfortunately for me, it did
> not.
>
> Can you advise me, how to approach this problem?
Yeah, don't :-) Really, loadavg is a stupid metric.
> I'm totally new to the scheduler code.
Luckily you won't actually have to touch much of it. Most of the actual
loadavg code lives in the first ~400 lines of kernel/sched/proc.c, read
and weep. Its one of the best documented bits around.
Your proposition however is extremely expensive, you turn something
that's already expensive O(nr_cpus) into something O(nr_cpus *
nr_cgroups).
I'm fairly sure people will not like that, esp. for something of such
questionable use as the loadavg -- its really only a pretty number that
doesn't mean all that much.
> -------- Original Message --------
> From: Li Zefan <lizefan@huawei.com>
>
> Then you should add Peter, Ingo and LKML to your Cc list. :)
You failed that, let me fix that.
next prev parent reply other threads:[~2014-01-13 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <529350DB.3010906@yuhu.biz>
[not found] ` <20131125150940.GB7120@sergelap>
[not found] ` <20131125151232.GR6766@redhat.com>
[not found] ` <52937B0C.3070005@yuhu.biz>
[not found] ` <52937B0C.3070005-NV7Lj0SOnH0@public.gmane.org>
2014-01-04 4:28 ` RFC: cgroups aware proc Marian Marinov
[not found] ` <52C78E09.60904-NV7Lj0SOnH0@public.gmane.org>
2014-01-05 0:12 ` Marian Marinov
[not found] ` <52C8A36B.6030201-NV7Lj0SOnH0@public.gmane.org>
2014-01-07 11:16 ` Li Zefan
2014-01-07 11:17 ` Li Zefan
[not found] ` <52CBE22F.1010106-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-01-07 17:42 ` Marian Marinov
[not found] ` <52CC3C80.8030603-NV7Lj0SOnH0@public.gmane.org>
2014-01-08 15:27 ` Serge Hallyn
2014-01-10 16:29 ` Marian Marinov
2014-01-13 3:26 ` Li Zefan
[not found] ` <52D41316.5080508@yuhu.biz>
2014-01-13 17:12 ` Peter Zijlstra [this message]
[not found] ` <20140113171238.GS31570-ndre7Fmf5hadTX5a5knrm8zTDFooKrT+cvkQGrU6aU0@public.gmane.org>
2014-01-14 0:58 ` Marian Marinov
[not found] ` <52D48BA6.2080701-NV7Lj0SOnH0@public.gmane.org>
2014-01-14 10:05 ` Peter Zijlstra
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=20140113171238.GS31570@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=berrange@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=lxc-devel@lists.linuxcontainers.org \
--cc=mingo@kernel.org \
--cc=mm@yuhu.biz \
--cc=serge.hallyn@ubuntu.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;
as well as URLs for NNTP newsgroup(s).