From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
bharata@linux.vnet.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Menage <menage@google.com>,
linux-kernel@vger.kernel.org,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Add hierarchical accounting to cpu accounting controller
Date: Thu, 30 Oct 2008 22:46:22 +0530 [thread overview]
Message-ID: <20081030171622.GA19872@linux.vnet.ibm.com> (raw)
In-Reply-To: <49057ADD.1050705@cn.fujitsu.com>
On Mon, Oct 27, 2008 at 04:25:01PM +0800, Li Zefan wrote:
> >>>> So in technical terms this patch looks fine now. There's still the
> >>>> question of whether it's OK to change the existing API, since it's
> >>>> been in the kernel in its currently (non-hierarchical) form for
> >>>> several releases now.
> >> Hmm... Can we consider this as an API change ? Currently cpuacct.usage
> >> readers of a parent accounting group are missing the usage contributions
> >> from its children groups. I would consider this patch as fixing the
> >> above problem by correctly reflecting the cpu usage for every accounting
> >> group.
> >>
> >
> > If a particular application desires to derive the usage of its
> > immediate tasks and does not care about subcgroups, it is a simple
> > iteration (after this fix)
> >
> > cpuacct - sigma(cpuacct_child)
> >
> > and currently if we cared about child accounting, we could do
> >
> > cpuacct + recursively(sigma(cpuacct_child))
> >
> > In that sense this fix makes more sense, but like Paul said we need to
> > figure out if it is an API change. My take is that it is a BUG fix,
> > since we do care about child subgroups in accounting.
> >
>
> cpuacct was designed to count cpu usage of a group of tasks, and now some people
> want it to also take child group's usage into account, so I think this is a feature
> request but not a bug fix.
>
I disagree. The child is a part of the parent's hierarchy, and therefore
its usage should reflect in the parent's usage.
Thanks,
--
regards,
Dhaval
next prev parent reply other threads:[~2008-10-30 17:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 5:43 [PATCH] Add hierarchical accounting to cpu accounting controller Bharata B Rao
2008-10-23 6:41 ` Bharata B Rao
2008-10-23 15:49 ` Paul Menage
2008-10-24 5:08 ` Bharata B Rao
2008-10-24 17:37 ` Paul Menage
2008-10-25 6:01 ` Bharata B Rao
2008-10-25 15:38 ` Paul Menage
2008-10-27 1:17 ` KAMEZAWA Hiroyuki
2008-10-27 4:43 ` Bharata B Rao
2008-10-27 6:57 ` Balbir Singh
2008-10-27 8:25 ` Li Zefan
2008-10-30 17:16 ` Dhaval Giani [this message]
2008-10-31 0:40 ` KAMEZAWA Hiroyuki
2008-11-04 12:49 ` Bharata B Rao
2008-11-04 17:20 ` Randy Dunlap
2008-11-05 3:24 ` Bharata B Rao
2008-11-05 3:29 ` Srivatsa Vaddagiri
2008-11-10 10:21 ` Dhaval Giani
2008-11-10 13:09 ` Ingo Molnar
2008-11-10 15:11 ` Bharata B Rao
2008-11-11 11:13 ` Ingo Molnar
2008-11-05 6:17 ` Li Zefan
2008-11-06 6:43 ` Balbir Singh
2008-11-10 10:22 ` Peter Zijlstra
2008-11-10 13:05 ` Balbir Singh
2008-11-05 3:31 ` Li Zefan
2008-11-05 3:48 ` KAMEZAWA Hiroyuki
2008-10-27 5:54 ` Li Zefan
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=20081030171622.GA19872@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.