From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <yellowdog-devel@lists.yellowdoglinux.com>,
"Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: SMP kernel configuration question?
Date: Sat, 16 Feb 2002 20:26:10 +0100 [thread overview]
Message-ID: <20020216192611.18399@smtp.wanadoo.fr> (raw)
In-Reply-To: <20020216144452.TKAF7187.tomts21-srv.bellnexxia.net@there>
>
>Hi,
>
>I have never configured a kernel for SMP before.
>
>I turned on the obvious CONFIG_SMP=y in the .config but was prompted if I
>would like to distribute interrupts (IRQs) across all CPUs.
>
>What is the recommended setting for:
>
>CONFIG_IRQ_ALL_CPUS
>
>Any guidance here would be greatly appreciated.
Leave it to N. ideally, you should enable it, but I have experienced
lockups when this feature is enabled, I haven't yet figured out what's
going on (could be related to the lockup some users are experiencing
with SMP + HIGHMEM on some dual 800, let me know if you see the same).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-16 19:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:08 new G4 dual 1 gig is here - how to install? Kevin B. Hendricks
2002-02-13 1:20 ` Tony 'Nicoya' Mantler
2002-02-13 1:55 ` Kevin B. Hendricks
2002-02-13 8:00 ` Olaf Hering
2002-02-13 13:49 ` Kevin B. Hendricks
2002-02-14 2:29 ` Kevin B. Hendricks
2002-02-14 3:53 ` Ani Joshi
2002-02-15 11:08 ` Kevin B. Hendricks
2002-02-16 9:30 ` Kevin B. Hendricks
2002-02-16 14:44 ` SMP kernel configuration question? Kevin B. Hendricks
2002-02-16 19:26 ` Benjamin Herrenschmidt [this message]
2002-02-16 15:39 ` SMP kernel seems to work fine Kevin B. Hendricks
2002-02-16 19:24 ` new G4 dual 1 gig is here - how to install? Benjamin Herrenschmidt
2002-02-14 13:53 ` Kevin B. Hendricks
2002-02-14 18:08 ` benh
2002-02-14 19:31 ` Christopher C. Chimelis
2002-02-13 2:25 ` Tom Rini
2002-02-13 5:37 ` Olaf Hering
2002-02-16 2:24 ` Kevin B. Hendricks
2002-02-16 19:19 ` Benjamin Herrenschmidt
2002-02-17 18:22 ` radeonfb.c flakiness Kevin B. Hendricks
2002-02-17 21:51 ` Benjamin Herrenschmidt
2002-02-18 20:55 ` Kevin B. Hendricks
2002-02-19 0:04 ` Benjamin Herrenschmidt
2002-02-16 23:59 ` question on best way to install other ide drives? Kevin B. Hendricks
2002-02-17 0:11 ` Tom Rini
2002-02-17 20:16 ` Timothy A. Seufert
2002-02-17 20:38 ` question: "disabling IRQ 54 defensively?" Kevin B. Hendricks
2002-02-17 21:53 ` Benjamin Herrenschmidt
2002-02-18 2:17 ` Final question: best wasy to move /, /usr, /home, etc? Kevin B. Hendricks
2002-02-18 2:36 ` Bastien Nocera
2002-02-18 16:16 ` Tom Rini
2002-02-18 16:20 ` Bastien Nocera
2002-02-18 3:12 ` Jeramy B. Smith
2002-02-18 8:42 ` Giuliano Pochini
2002-02-18 14:52 ` Derrik Pates
2002-02-18 15:05 ` Gabriel Paubert
2002-02-18 23:18 ` Michael Heironimus
2002-02-18 17:31 ` David A. Gatwood
2002-02-17 21:52 ` question on best way to install other ide drives? Benjamin Herrenschmidt
2002-02-17 23:19 ` Tom Rini
2002-02-16 2:40 ` Weird bug problems with timing of NIC driver loading? Kevin B. Hendricks
2002-02-16 19:22 ` Benjamin Herrenschmidt
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=20020216192611.18399@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-devel@lists.yellowdoglinux.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;
as well as URLs for NNTP newsgroup(s).