OpenVZ Forum - RDF feed
type: channel
items: Re: [PATCH 1/7] cgroup: fix and update documentation

Re: [PATCH 1/7] cgroup: fix and update documentation
type: item
description: Li Zefan wrote: > *** notify_on_release is disabled in the current patch set. It will be > -*** reactivated in a future patch in a less-intrusive manner > +*** reactivated in a future patch in a less-intrusive manner. Someone should verify this, but I'm pretty sure that notify_on_release is now working ... no longer disabled. I believe the above line from the documentation is out of date. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.940.382.4214 _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Paul Jackson
date: 2008-02-18T07:02:54-00:00

Re: [PATCH 1/7] cgroup: fix and update documentation
type: item
description: Paul Jackson wrote: > Li Zefan wrote: >> *** notify_on_release is disabled in the current patch set. It will be >> -*** reactivated in a future patch in a less-intrusive manner >> +*** reactivated in a future patch in a less-intrusive manner. > > Someone should verify this, but I'm pretty sure that notify_on_release > is now working ... no longer disabled. I believe the above line from > the documentation is out of date. > Aha, it does work now. I tried it but it didn't seem to work, maybe I didn't something wrong. I'll resend a new patch. _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Li Zefan
date: 2008-02-18T08:25:14-00:00

Re: [PATCH 1/7] cgroup: fix and update documentation
type: item
description: Misc fixes and updates, make the doc consistent with current cgroup implementation. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- Documentation/cgroups.txt | 66 ++++++++++++++++++++++---------------------- 1 files changed, 33 insertions(+), 33 deletions(-) diff --git a/Documentation/cgroups.txt b/Documentation/cgroups.txt index 42d7c4c..31d12e2 100644 --- a/Documentation/cgroups.txt +++ b/Documentation/cgroups.txt @@ -28,7 +28,7 @@ CONTENTS: 4. Questions 1. Control Groups -========== +================= 1.1 What are cgroups ? ---------------------- @@ -143,10 +143,10 @@ proliferation of such cgroups. Also lets say that the administrator would like to give enhanced network access temporarily to a student's browser (since it is night and the user -wants to do online gaming :) OR give one of the students simulation +wants to do online gaming :)) OR give one of the students simulation apps enhanced CPU power, -With ability to write pids directly to resource classes, its just a +With ability to write pids directly to resource classes, it's just a matter of : # echo pid > /mnt/network/<new_class>/tasks @@ -227,10 +227,13 @@ Each cgroup is represented by a directory in the cgroup file system containing the following files describing that cgroup: - tasks: list of tasks (by pid) attached to that cgroup - - notify_on_release flag: run /sbin/cgroup_release_agent on exit? + - releasable flag: cgroup currently removeable? + - notify_on_release flag: run the release agent on exit? + - release_agent: the path to use for release notifications (this file + exists in the top cgroup only) Other subsystems such as cpusets may add additional files in each -cgroup dir +cgroup dir. New cgroups are created using the mkdir system call or shell command. The properties of a cgroup, such as its flags, are @@ -257,7 +260,7 @@ performance. To allow access from a cgroup to the css_sets (and hence tasks) that comprise it, a set of cg_cgroup_link objects form a lattice; each cg_cgroup_link is li…
creator: Li Zefan
date: 2008-02-18T08:39:15-00:00

Re: [PATCH 1/7] cgroup: fix and update documentation
type: item
description: On Feb 18, 2008 12:39 AM, Li Zefan <lizf@cn.fujitsu.com> wrote: > Misc fixes and updates, make the doc consistent with current > cgroup implementation. > > Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> Acked-by: Paul Menage <menage@google.com> Thanks for these cleanups. Paul > --- > Documentation/cgroups.txt | 66 ++++++++++++++++++++++---------------------- > 1 files changed, 33 insertions(+), 33 deletions(-) > > diff --git a/Documentation/cgroups.txt b/Documentation/cgroups.txt > index 42d7c4c..31d12e2 100644 > > --- a/Documentation/cgroups.txt > +++ b/Documentation/cgroups.txt > @@ -28,7 +28,7 @@ CONTENTS: > 4. Questions > > 1. Control Groups > -========== > +================= > > 1.1 What are cgroups ? > ---------------------- > @@ -143,10 +143,10 @@ proliferation of such cgroups. > > Also lets say that the administrator would like to give enhanced network > access temporarily to a student's browser (since it is night and the user > -wants to do online gaming :) OR give one of the students simulation > +wants to do online gaming :)) OR give one of the students simulation > apps enhanced CPU power, > > -With ability to write pids directly to resource classes, its just a > +With ability to write pids directly to resource classes, it's just a > matter of : > > # echo pid > /mnt/network/<new_class>/tasks > @@ -227,10 +227,13 @@ Each cgroup is represented by a directory in the cgroup file system > containing the following files describing that cgroup: > > - tasks: list of tasks (by pid) attached to that cgroup > - - notify_on_release flag: run /sbin/cgroup_release_agent on exit? > + - releasable flag: cgroup currently removeable? > + - notify_on_release flag: run the release agent on exit? > + - release_agent: the path to use for release notifications (this file > + exists in the top cgroup only) > > Other subsystems such as cpusets may add additional files in each > -cgroup dir > +cgroup dir. > > New cgroups are created using the mkdir system call or shell > command.…
creator: Paul Menage
date: 2008-02-20T03:08:21-00:00