OpenVZ Forum


Home » Mailing lists » Devel » [RFC][PATCH 0/7] CGroup API: More structured API for CGroups control files
Re: [RFC][PATCH 1/7] CGroup API: Add cgroup.api control file [message #27392 is a reply to message #27390] Sat, 16 February 2008 17:44 Go to previous messageGo to previous message
Paul Menage is currently offline  Paul Menage
Messages: 642
Registered: September 2006
Senior Member
On Feb 16, 2008 2:07 AM, Balbir Singh <balbir@linux.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
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [PATCH 1/7] cgroup: fix and update documentation
Next Topic: [PATCH] [NETNS]: Namespace leak in pneigh_lookup.
Goto Forum:
  


Current Time: Thu Jul 18 01:40:55 GMT 2024

Total time taken to generate the page: 0.02586 seconds