From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Paul Menage <menage@google.com>,
containers@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Revert for cgroups CPU accounting subsystem patch
Date: Tue, 13 Nov 2007 13:29:46 +0530 [thread overview]
Message-ID: <20071113075946.GA14731@linux.vnet.ibm.com> (raw)
In-Reply-To: <47395277.1060006@linux.vnet.ibm.com>
On Tue, Nov 13, 2007 at 12:59:59PM +0530, Balbir Singh wrote:
> Paul Menage wrote:
> > On Nov 12, 2007 11:00 PM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >> Right now, one of the limitations of the CPU controller is that
> >> the moment you create another control group, the bandwidth gets
> >> divided by the default number of shares. We can't create groups
> >> just for monitoring.
> >
> > Could we get around this with, say, a flag that always treats a CFS
> > schedulable entity as having a weight equal to the number of runnable
> > tasks in it? So CPU bandwidth would be shared between groups in
> > proportion to the number of runnable tasks, which would distribute the
> > cycles approximately equivalently to them all being separate
> > schedulable entities.
> >
>
> I think it's a good hack, but not sure about the complexity to implement
> the code.
I agree that it would be adding unnecessary complexity, just to meet the
accounting needs.
Thinking of it more, this requirement to "group tasks for only accounting
purpose" may be required for other resources (mem, io, network etc) as well?
Should we have a generic accounting controller which can provide these
various resource usgae stats for a group (cpu, mem etc) by iterating thr' the
task list for the group and summing up the corresponding stats already present
in task structure?
--
Regards,
vatsa
next prev parent reply other threads:[~2007-11-13 7:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 5:25 Revert for cgroups CPU accounting subsystem patch Paul Menage
2007-11-13 6:00 ` Srivatsa Vaddagiri
2007-11-13 6:05 ` Paul Menage
2007-11-13 7:00 ` Balbir Singh
2007-11-13 7:10 ` Paul Menage
2007-11-13 7:29 ` Balbir Singh
2007-11-13 7:34 ` Paul Menage
2007-11-13 7:59 ` Srivatsa Vaddagiri [this message]
2007-11-13 7:59 ` Paul Menage
2007-11-13 7:48 ` Srivatsa Vaddagiri
2007-11-13 7:57 ` Paul Menage
2007-11-29 19:17 ` [PATCH] sched: cpu accounting controller Srivatsa Vaddagiri
2007-11-29 19:20 ` Ingo Molnar
2007-11-29 19:39 ` Srivatsa Vaddagiri
2007-11-29 19:30 ` Andrew Morton
2007-11-29 20:18 ` Srivatsa Vaddagiri
2007-11-30 12:42 ` [PATCH] sched: cpu accounting controller (V2) Srivatsa Vaddagiri
2007-11-30 12:35 ` Ingo Molnar
2007-11-30 13:09 ` Srivatsa Vaddagiri
2007-11-30 13:34 ` Ingo Molnar
2007-11-30 12:45 ` Balbir Singh
2007-11-30 13:53 ` Ingo Molnar
2007-11-30 14:00 ` Balbir Singh
2007-11-30 18:45 ` Balbir Singh
2007-11-30 19:46 ` Ingo Molnar
2007-12-01 7:48 ` Paul Menage
2007-12-01 9:51 ` Balbir Singh
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=20071113075946.GA14731@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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