From: Marian Marinov <mm@yuhu.biz>
To: Peter Zijlstra <peterz@infradead.org>
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: RFC: cgroups aware proc
Date: Tue, 14 Jan 2014 02:58:14 +0200 [thread overview]
Message-ID: <52D48BA6.2080701@yuhu.biz> (raw)
In-Reply-To: <20140113171238.GS31570@twins.programming.kicks-ass.net>
On 01/13/2014 07:12 PM, Peter Zijlstra wrote:
> 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.
Yes... stupid, but unfortunately everyone is looking at it :(
>
>> 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.
I looked trough it but I don't understand how to introduce the per cgroup calculation.
I looked trough the headers and found the following, which is already implemented.
task->sched_task_group->load_avg
task->sched_task_group->cfs_rq->load_avg
task->sched_task_group->cfs_rq->load.weight
task->sched_task_group->cfs_rq->runnable_load_avg
Unfortunately there is almost no documentation for these elements of the cfs_rq and task_group structs.
It seams to me that part of the per task group loadavg code is already present.
>
> 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.
I know that its use is questionable but in my case I need to have it, or I will not be able to offer correct loadavg
values in the containers.
>
>> -------- 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-14 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52D35CD0.9070602@huawei.com>
[not found] ` <52D41316.5080508@yuhu.biz>
2014-01-13 17:12 ` Fwd: " Peter Zijlstra
2014-01-14 0:58 ` Marian Marinov [this message]
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=52D48BA6.2080701@yuhu.biz \
--to=mm@yuhu.biz \
--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=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®