From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: mark irqbalance not-recommended
Date: Tue, 23 Oct 2007 13:57:09 +0200 [thread overview]
Message-ID: <20071023115709.GA1734@elf.ucw.cz> (raw)
Mark CONFIG_IRQBALANCE as not recommended any more. It eats too much
power, and better solutions are available in userspace.
Signed-off-by: Pavel Machek <pavel@suse.cz>
---
commit 2665f7971b5b97830b028308553a78a95c131988
tree e1782cceebfb5900373469c0043d113de88f861f
parent f5085f6ea1c5771708c44a4a42ee217e760ff4a0
author Pavel <pavel@amd.ucw.cz> Tue, 23 Oct 2007 13:56:15 +0200
committer Pavel <pavel@amd.ucw.cz> Tue, 23 Oct 2007 13:56:15 +0200
arch/i386/Kconfig | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig
index eba2d88..10f3c38 100644
--- a/arch/i386/Kconfig
+++ b/arch/i386/Kconfig
@@ -779,10 +779,13 @@ config EFI
config IRQBALANCE
bool "Enable kernel irq balancing"
depends on SMP && X86_IO_APIC
- default y
+ default n
help
- The default yes will allow the kernel to do irq load balancing.
- Saying no will keep the kernel from doing irq load balancing.
+ Saying yes will allow the kernel to do irq load balancing;
+ but it generates too many CPU wakeups, eating power, and
+ is better done in userspace.
+
+ Say N.
# turning this on wastes a bunch of space.
# Summit needs it only when NUMA is on
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2007-10-23 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 11:57 Pavel Machek [this message]
2007-10-23 13:05 ` mark irqbalance not-recommended Adrian Bunk
2007-10-23 16:00 ` Arjan van de Ven
2007-10-23 20:42 ` Jeff Garzik
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=20071023115709.GA1734@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.