mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: torvalds <torvalds@linux-foundation.org>,
	Geunsik Lim <geunsik.lim@samsung.com>,
	Paul Menage <menage@google.com>
Subject: [PATCH 8/8] Documentation: update cgroups info user groups names
Date: Mon, 4 Apr 2011 15:10:45 -0700	[thread overview]
Message-ID: <20110404151045.89e63510.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110404145803.8663081d.rdunlap@xenotime.net>

From: Geunsik Lim <geunsik.lim@samsung.com>

Update suitable words to explain / understand cgroups contents.

Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
Cc: Paul Menage <menage@google.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/cgroups/cgroups.txt |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

--- linux-2.6.38-git18.orig/Documentation/cgroups/cgroups.txt
+++ linux-2.6.38-git18/Documentation/cgroups/cgroups.txt
@@ -110,22 +110,22 @@ university server with various users - s
 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.

      parent reply	other threads:[~2011-04-04 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 21:58 [PATCH 1/8] Documentation: update kmemleak arch. info Randy Dunlap
2011-04-04 21:59 ` [PATCH 2/8] kernel/signal.c: fix typos and coding style Randy Dunlap
2011-04-04 22:00 ` [PATCH 3/8] kernel/signal.c: add kernel-doc notation to syscalls Randy Dunlap
2011-04-05  8:32   ` Matt Fleming
2011-04-08 17:41     ` Randy Dunlap
2011-04-08 17:53     ` [PATCH] signal.c: fix erroneous syscall kernel-doc Randy Dunlap
2011-04-08 20:13       ` Matt Fleming
2011-04-04 22:02 ` [PATCH 4/8] Documentation: update panic parameter info Randy Dunlap
2011-04-04 22:04 ` [PATCH 5/8] Documentation: fix minor typos/spelling Randy Dunlap
2011-04-04 22:06 ` [PATCH 6/8] kemleak-test: build as module only Randy Dunlap
2011-04-04 22:08 ` [PATCH 7/8] Documentation: consolidate leds files to leds/ subdir Randy Dunlap
2011-04-05  0:54   ` Linus Torvalds
2011-04-05  8:25     ` Antonio Ospite
2011-04-04 22:10 ` 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=20110404151045.89e63510.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=geunsik.lim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=torvalds@linux-foundation.org \
    /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®