* [PATCH v2] cgroup-doc: suitable words to explain cgroups.
@ 2011-03-30 15:11 Geunsik Lim
2011-03-31 17:01 ` Randy Dunlap
0 siblings, 1 reply; 2+ messages in thread
From: Geunsik Lim @ 2011-03-30 15:11 UTC (permalink / raw)
To: Paul Menage
Cc: Jiri Kosina, linux-kernel, Srivatsa Vaddagiri, Randy Dunlap,
Andrew Morton
Update suitable words to explain / understand cgroups contents.
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
Cc: Paul Menage <menage@google.com>
---
Documentation/cgroups/cgroups.txt | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
index cbdfb7d..aedf1bd 100644
--- a/Documentation/cgroups/cgroups.txt
+++ b/Documentation/cgroups/cgroups.txt
@@ -110,22 +110,22 @@ university server with various users - students, professors, system
tasks etc. The resource planning for this server could be along the
following lines:
- CPU : Top cpuset
+ CPU : "Top cpuset"
/ \
CPUSet1 CPUSet2
- | |
- (Profs) (Students)
+ | |
+ (Professors) (Students)
In addition (system tasks) are attached to topcpuset (so
that they can run anywhere) with a limit of 20%
- Memory : Professors (50%), students (30%), system (20%)
+ Memory : Professors (50%), Students (30%), system (20%)
- Disk : Prof (50%), students (30%), system (20%)
+ Disk : Professors (50%), Students (30%), system (20%)
Network : WWW browsing (20%), Network File System (60%), others (20%)
/ \
- Prof (15%) students (5%)
+ Professors (15%) students (5%)
Browsers like Firefox/Lynx go into the WWW network class, while (k)nfsd go
into NFS network class.
--
1.7.3
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v2] cgroup-doc: suitable words to explain cgroups.
2011-03-30 15:11 [PATCH v2] cgroup-doc: suitable words to explain cgroups Geunsik Lim
@ 2011-03-31 17:01 ` Randy Dunlap
0 siblings, 0 replies; 2+ messages in thread
From: Randy Dunlap @ 2011-03-31 17:01 UTC (permalink / raw)
To: Geunsik Lim
Cc: Paul Menage, Jiri Kosina, linux-kernel, Srivatsa Vaddagiri,
Andrew Morton
On Thu, 31 Mar 2011 00:11:39 +0900 Geunsik Lim wrote:
> Update suitable words to explain / understand cgroups contents.
>
> Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
> Cc: Paul Menage <menage@google.com>
Applied to the documentation patch queue. Thanks.
> ---
> Documentation/cgroups/cgroups.txt | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> index cbdfb7d..aedf1bd 100644
> --- a/Documentation/cgroups/cgroups.txt
> +++ b/Documentation/cgroups/cgroups.txt
> @@ -110,22 +110,22 @@ university server with various users - students, professors, system
> tasks etc. The resource planning for this server could be along the
> following lines:
>
> - CPU : Top cpuset
> + CPU : "Top cpuset"
> / \
> CPUSet1 CPUSet2
> - | |
> - (Profs) (Students)
> + | |
> + (Professors) (Students)
>
> In addition (system tasks) are attached to topcpuset (so
> that they can run anywhere) with a limit of 20%
>
> - Memory : Professors (50%), students (30%), system (20%)
> + Memory : Professors (50%), Students (30%), system (20%)
>
> - Disk : Prof (50%), students (30%), system (20%)
> + Disk : Professors (50%), Students (30%), system (20%)
>
> Network : WWW browsing (20%), Network File System (60%), others (20%)
> / \
> - Prof (15%) students (5%)
> + Professors (15%) students (5%)
>
> Browsers like Firefox/Lynx go into the WWW network class, while (k)nfsd go
> into NFS network class.
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-03-31 17:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-30 15:11 [PATCH v2] cgroup-doc: suitable words to explain cgroups Geunsik Lim
2011-03-31 17:01 ` Randy Dunlap
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®