From: Max Krasnyansky <maxk@qualcomm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl, pj@sgi.com,
Max Krasnyansky <maxk@qualcomm.com>
Subject: [PATCH sched-devel 6/7] cpuisol: Minor updates to the Kconfig options
Date: Fri, 22 Feb 2008 13:09:17 -0800 [thread overview]
Message-ID: <1203714558-20904-6-git-send-email-maxk@qualcomm.com> (raw)
In-Reply-To: <1203714558-20904-5-git-send-email-maxk@qualcomm.com>
Fixed a couple of typos, long lines and referred to the documentation file.
Signed-off-by: Max Krasnyansky <maxk@qualcomm.com>
---
kernel/Kconfig.cpuisol | 31 +++++++++++++++++--------------
1 files changed, 17 insertions(+), 14 deletions(-)
diff --git a/kernel/Kconfig.cpuisol b/kernel/Kconfig.cpuisol
index 81f1972..e681b02 100644
--- a/kernel/Kconfig.cpuisol
+++ b/kernel/Kconfig.cpuisol
@@ -2,23 +2,26 @@ config CPUISOL
depends on SMP
bool "CPU isolation"
help
- This option enables support for CPU isolation.
- If enabled the kernel will try to avoid kernel activity on the isolated CPUs.
- By default user-space threads are not scheduled on the isolated CPUs unless
- they explicitly request it (via sched_ and pthread_ affinity calls). Isolated
- CPUs are not subject to the scheduler load-balancing algorithms.
-
- CPUs can be marked as isolated using 'isolcpus=' command line option or by
- writing '1' into /sys/devices/system/cpu/cpuN/isolated.
-
- This feature is useful for hard realtime and high performance applications.
+ This option enables support for CPU isolation. If enabled the
+ kernel will try to avoid kernel activity on the isolated CPUs.
+ By default user-space threads are not scheduled on the isolated
+ CPUs unless they explicitly request it via sched_setaffinity()
+ and pthread_setaffinity_np() calls. Isolated CPUs are not
+ subject to the scheduler load-balancing algorithms.
+
+ This feature is useful for hard realtime and high performance
+ applications.
+ See Documentation/cpu-isolation.txt for more details.
+
If unsure say 'N'.
config CPUISOL_WORKQUEUE
bool "Do not schedule workqueues on the isolated CPUs (EXPERIMENTAL)"
depends on CPUISOL && EXPERIMENTAL
help
- In this option is enabled kernel will not schedule workqueues on the
- isolated CPUs.
- Please note that at this point this feature is experimental. It brakes
- certain things like OProfile that heavily rely on per cpu workqueues.
+ If this option is enabled kernel will not schedule workqueues on
+ the isolated CPUs. Please note that at this point this feature
+ is experimental. It breaks certain things like OProfile that
+ heavily rely on per cpu workqueues.
+
+ Say 'Y' to enable workqueue isolation. If unsure say 'N'.
--
1.5.4.1
next prev parent reply other threads:[~2008-02-22 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 21:09 [PATCH sched-devel 1/7] cpuisol: Make cpu isolation configrable and export isolated map Max Krasnyansky
2008-02-22 21:09 ` [PATCH sched-devel 2/7] cpuisol: Do not route IRQs to the CPUs isolated at boot Max Krasnyansky
2008-02-22 21:09 ` [PATCH sched-devel 3/7] cpuisol: Do not schedule workqueues on the isolated CPUs Max Krasnyansky
2008-02-22 21:09 ` [PATCH sched-devel 4/7] cpuisol: Move on-stack array used for boot cmd parsing into __initdata Max Krasnyansky
2008-02-22 21:09 ` [PATCH sched-devel 5/7] cpuisol: Documentation updates Max Krasnyansky
2008-02-22 21:09 ` Max Krasnyansky [this message]
2008-02-22 21:09 ` [PATCH sched-devel 7/7] cpuisol: Do not halt isolated CPUs with Stop Machine Max Krasnyansky
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=1203714558-20904-6-git-send-email-maxk@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.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®