mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Geunsik Lim <leemgs1@gmail.com>
Cc: Paul Menage <menage@google.com>, Jiri Kosina <trivial@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] cgroup-doc: suitable words to explain cgroups.
Date: Thu, 31 Mar 2011 10:01:54 -0700	[thread overview]
Message-ID: <20110331100154.56cfd67f.rdunlap@xenotime.net> (raw)
In-Reply-To: <1301497899-15322-1-git-send-email-leemgs1@gmail.com>

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 ***

      reply	other threads:[~2011-03-31 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 15:11 Geunsik Lim
2011-03-31 17:01 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110331100154.56cfd67f.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=leemgs1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=trivial@kernel.org \
    --cc=vatsa@in.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®