| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 8 Apr 2008 22:02:30 +0530 From: Balaji Rao <balajirrao@...il.com> To: "Paul Menage" <menage@...gle.com> Cc: linux-kernel@...r.kernel.org, containers@...ts.osdl.org, dhaval@...ux.vnet.ibm.com, balbir@...ibm.com, a.p.zijlstra@...llo.nl, "Ingo Molnar" <mingo@...e.hu> Subject: Re: [RFC][-mm] [0/2] Basic stats for cgroups V2 On Tuesday 08 April 2008 08:22:16 pm Paul Menage wrote: > On Tue, Apr 8, 2008 at 6:49 AM, Balaji Rao <balajirrao@...il.com> wrote: > > > > We are also looking at a generic framework in cgroups that would delegate the > > job of handling statistics to the cgroup framework itself. This would avoid > > code duplication across various controllers. > > Yes, avoiding code duplication is good. > > On thing - when you say "statistics" do you mean all statistics (i.e. > all values that can be read from control files) or specifically > arrays/maps of values in specific control files? I'm using it to mean > the former, but you appear to be mostly referring to stats maps such > as "memory.stat" or "cpu.stat". Sorry for the confusion. You're right. I'm speaking about the "cpu.stat" and "memory.stat" idea. What we want is, a layer above the generic file presentation layer, that would collect and manage the statistics the controllers would provide. -- regards, Balaji Rao Dept. of Mechanical Engineering, National Institute of Technology Karnataka, India -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists