All of
 help / color / mirror / Atom feed
From: Andrew Morton <>
To: Pavel Emelianov <>
Cc: Paul Menage <>, Balbir Singh <>,
	Linux Kernel Mailing List <>,, Kirill Korotaev <>,
	Srivatsa Vaddagiri <>
Subject: Re: [PATCH] Cpu statistics accounting based on Paul Menage patches
Date: Wed, 11 Apr 2007 11:49:27 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 11 Apr 2007 19:02:27 +0400
Pavel Emelianov <> wrote:

> Provides a per-container statistics concerning the numbers of tasks
> in various states, system and user times, etc. Patch is inspired
> by Paul's example of the used CPU time accounting. Although this
> patch is independent from Paul's example to make it possible playing
> with them separately.

Why is this actually needed?  If userspace has a list of the tasks which
are in a particular container, it can run around and add up the stats for
those tasks without kernel changes?

It's a bit irksome that we have so much accounting of this form in core
kernel, yet we have to go and add a completely new implementation to create
something which is similar to what we already have.  But I don't
immediately see a fix for that.  Apart from paragraph #1 ;)

Should there be linkage between per-container stats and
delivery-via-taskstats?  I can't think of one, really.

You have cpu stats.  Later, presumably, we'll need IO stats, MM stats,
context-switch stats, number-of-syscall stats, etc, etc.  Are we going to
reimplement all of those things as well?  See paragraph #1!

Bottom line: I think we seriously need to find some way of consolidating
per-container stats with our present per-task stats.  Perhaps we should
instead be looking at ways in which we can speed up paragraph #1.

  reply	other threads:[~2007-04-11 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 15:02 [PATCH] Cpu statistics accounting based on Paul Menage patches Pavel Emelianov
2007-04-11 18:49 ` Andrew Morton [this message]
2007-04-12 16:23   ` Pavel Emelianov
2007-04-12 21:00   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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.