From: Stephen Hemminger <shemminger@osdl.org>
To: Simon Derr <Simon.Derr@bull.net>
Cc: linux-kernel@vger.kernel.org
Subject: (2/4) [PATCH] cpuset - Kconfig
Date: Tue, 21 Oct 2003 16:20:27 -0700 [thread overview]
Message-ID: <20031021162027.56f90c38.shemminger@osdl.org> (raw)
In-Reply-To: <Pine.A41.4.53.0310131503500.173334@isabelle.frec.bull.fr>
Here is an improvement to your Kconfig entry.
1. Use dependencies rather than using an 'if x86 || IA64' around it.
2. It is certainly experimental at this point
3. Better descriptive text (hopefully)
4. Let the config system do the PROC_FS dependency, not the human.
diff -Nru a/init/Kconfig b/init/Kconfig
--- a/init/Kconfig Tue Oct 21 16:07:24 2003
+++ b/init/Kconfig Tue Oct 21 16:07:24 2003
@@ -194,28 +194,28 @@
Disabling this option will cause the kernel to be built without
support for epoll family of system calls.
-if X86 || IA64
-
config CPUSETS
- bool "cpusets"
- depends on SMP
+ bool "Cpuset support"
+ depends on SMP && (X86 || IA64) && EXPERIMENTAL
help
- This options will let you create and manage sets of cpu where you
- can run the processes.
+ This options will let you create and manage CPUSET's which
+ allow partioning a SMP machine into execution areas. Processes
+ in a CPUSET are not allowed to run on processor's outside
+ the given group.
Say N if unsure.
config CPUSETS_PROC
bool "/proc/cpusets support"
- depends on CPUSETS
+ depends on CPUSETS && PROC_FS
+ default y
help
Get some info about the existing cpusets in your system.
- To use this option, you have to ensure that the "/proc file system
- support" (CONFIG_PROC_FS) is enabled, too.
config CPUSETS_PROC_CPUINFO
bool "/proc/cpuinfo uses current cpuset"
depends on CPUSETS_PROC
+ default y
help
With this option enabled, a process reading /proc/cpuinfo will
only see the CPUs that are in its current cpuset.
@@ -223,11 +223,11 @@
config CPUSETS_PROC_STAT
bool "/proc/stat uses current cpuset"
depends on CPUSETS_PROC
+ default y
help
With this option enabled, a process reading /proc/stat will
only see the CPUs that are in its current cpuset.
-endif
source "drivers/block/Kconfig.iosched"
next prev parent reply other threads:[~2003-10-21 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 13:07 [RFC] cpuset proposal Simon Derr
2003-10-21 23:20 ` (1/4) [PATCH] cpuset -- 2.6.0-test8 Stephen Hemminger
2003-10-22 0:08 ` William Lee Irwin III
2003-10-22 14:34 ` Simon Derr
2003-10-22 14:57 ` William Lee Irwin III
2003-10-21 23:20 ` Stephen Hemminger [this message]
2003-10-21 23:20 ` (3/4) [PATCH] cpuset - build without CPUSET configured Stephen Hemminger
2003-10-21 23:20 ` (4/4) [PATCH] cpuset -- seqfile change Stephen Hemminger
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=20031021162027.56f90c38.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=Simon.Derr@bull.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).