public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 4/7] Add Documentation for FAIR_USER_SCHED sysfs files
Date: Mon, 17 Dec 2007 12:33:20 -0800	[thread overview]
Message-ID: <1197923603-6752-4-git-send-email-gregkh@suse.de> (raw)
In-Reply-To: <20071217185654.GC4330@kroah.com>

From: Dhaval Giani <dhaval@linux.vnet.ibm.com>

This patch adds documentation about /sys/kernel/uids/<uid>/cpu_share
to Documentation/ABI.

Signed-off-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
 Documentation/ABI/testing/sysfs-kernel-uids |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-kernel-uids

diff --git a/Documentation/ABI/testing/sysfs-kernel-uids b/Documentation/ABI/testing/sysfs-kernel-uids
new file mode 100644
index 0000000..648d65d
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-uids
@@ -0,0 +1,14 @@
+What:		/sys/kernel/uids/<uid>/cpu_shares
+Date:		December 2007
+Contact:	Dhaval Giani <dhaval@linux.vnet.ibm.com>
+		Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
+Description:
+		The /sys/kernel/uids/<uid>/cpu_shares tunable is used
+		to set the cpu bandwidth a user is allowed. This is a
+		propotional value. What that means is that if there
+		are two users logged in, each with an equal number of
+		shares, then they will get equal CPU bandwidth. Another
+		example would be, if User A has shares = 1024 and user
+		B has shares = 2048, User B will get twice the CPU
+		bandwidth user A will. For more details refer
+		Documentation/sched-design-CFS.txt
-- 
1.5.3.7


  parent reply	other threads:[~2007-12-17 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 18:56 [GIT PATCH] driver core and documentation fixes for 2.6.24-rc5 Greg KH
2007-12-17 20:33 ` [PATCH 1/7] kobject: fix the documentation of how kobject_set_name works Greg Kroah-Hartman
2007-12-17 20:33 ` [PATCH 2/7] tipar: remove obsolete module Greg Kroah-Hartman
2007-12-17 20:33 ` Greg Kroah-Hartman [this message]
2007-12-17 20:33 ` [PATCH 5/7] HOWTO: change addresses of maintainer and lxr url for Korean HOWTO Greg Kroah-Hartman
2007-12-17 20:33 ` [PATCH 6/7] add stable_api_nonsense.txt in korean Greg Kroah-Hartman
2007-12-17 20:33 ` [PATCH 7/7] HOWTO: update misspelling and word incorrected Greg Kroah-Hartman
2007-12-18  0:15 ` [GIT PATCH] driver core and documentation fixes for 2.6.24-rc5 Andrew Morton

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=1197923603-6752-4-git-send-email-gregkh@suse.de \
    --to=gregkh@suse.de \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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