| 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 19:19:14 +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 01:06:17 pm Paul Menage wrote: > > One of the important API choices would be whether the stats API was > fixed in header files shared with userspace, or whether it would be > possible for stats to be added and dynamically discovered/used by > userspace without needing fixed header file descriptions. > The second idea is much better, I feel. > The difference would be a bit like the old sysctl API (where each > sysctl entry had to be enumerated in a header file) versus the newer > /proc/sys approach where numerical values aren't used and userspace > can determine which entries are supported at runtime, and even access > new previously-unknown entries. > <snip> > > Thoughts? Overall the idea looks good to me. 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. -- regards, Balaji Rao -- 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