On Wed, 11 Apr 2007 19:02:27 +0400
Pavel Emelianov <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
