> I was kind of thinking that the stats should be per-process (actually
> per-mm) rather than bound to cpusets. /proc/<pid>/pageout-stats or something.
The particular people that I deal with care about constraining things
on a per-cpuset basis, so that is the information that I personally am
looking for. But it is simple enough to map tasks to cpusets and vice-versa,
so this is not really a serious consideration. I would generically be in
favor of the per-process stats (even though the application at hand is
actually interested in the cpuset aggregate stats), because we can always
produce an aggregate from the detailed, but not vice-versa. And no doubt
some future as-yet-unimagined application will want per-process info.
--
Bron Campbell Nelson [email protected]
These statements are my own, not those of Silicon Graphics.
-
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]
