| 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
| ||
|
Message-ID: <6599ad830802160944v6d529570k1ade6df273ca3d0d@mail.gmail.com> Date: Sat, 16 Feb 2008 09:44:40 -0800 From: "Paul Menage" <menage@...gle.com> To: balbir@...ux.vnet.ibm.com Cc: balbir@...ibm.com, pj@....com, "Pavel Emelianov" <xemul@...nvz.org>, "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>, vatsa@...ux.vnet.ibm.com, akpm@...ux-foundation.org, containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [RFC][PATCH 1/7] CGroup API: Add cgroup.api control file On Feb 16, 2008 2:07 AM, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote: > Paul Menage wrote: > > Hi, Paul, > > Do we need to use a cgroup.api file? Why not keep up to date documentation and > get users to use that. I fear that, cgroup.api will not be kept up-to-date, > leading to confusion. The cgroup.api file isn't meant to give complete documentation for a control file, simply a brief indication of its usage. The aim is that most bits of the information reported in cgroup.api are auto-generated, so there shouldn't be problems with it getting out-of-date. Is it just the space used by the documentation string that you're objecting to? The other function of the file is to declare a type for each variable. Paul -- 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