From: William Lee Irwin III <wli@holomorphy.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
LSE <lse-tech@lists.sourceforge.net>,
Mark Haverkamp <markh@osdl.org>
Subject: Re: [Lse-tech] [PATCH][ANNOUNCE] 32way/8quad NUMAQ booting with 16 IOAPICs, 223 IRQs
Date: Sun, 16 Mar 2003 21:54:15 -0800 [thread overview]
Message-ID: <20030317055415.GM5891@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303071148150.18716-100000@montezuma.mastecende.com>
On Mon, Mar 17, 2003 at 12:21:42AM -0500, Zwane Mwaikambo wrote:
> I've managed to put together a patch which allows a NUMAQ box with
> more than 8 IOAPICs to boot, the current workaround is to force it to 8
> or lower. This was achieved by setting up percpu idts thus allowing
> us to implement per node vector spaces. The previous hurdle was running out
> of vectors to assign, the current one is running out of irqs, something
> which i'll further be looking at.
> Later on i'm planning to move to per node IDTs so that i can fix f00f
> workaround and also save space on nodeless systems. To do this will
> probably require early_cpu_to_node workalikes (or perhaps just use
> logical_smp_processor_id and apic_to_node).
> Thanks to the folks at OSDL (and Mark for giving up his 4quad for so
> long) for providing me access to the 8quad.
Running out of IRQ's? Simply jacking up NR_IRQS and HARDIRQ_BITS should
suffice if this is what I think it is.
-- wli
next prev parent reply other threads:[~2003-03-17 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 5:21 [PATCH][ANNOUNCE] 32way/8quad NUMAQ booting with 16 IOAPICs, 223 IRQs Zwane Mwaikambo
2003-03-17 5:54 ` William Lee Irwin III [this message]
2003-03-17 6:11 ` [Lse-tech] " Zwane Mwaikambo
2003-03-17 6:28 ` William Lee Irwin III
2003-03-17 7:28 ` Zwane Mwaikambo
2003-03-17 7:41 ` William Lee Irwin III
2003-03-17 8:15 ` Zwane Mwaikambo
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=20030317055415.GM5891@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=markh@osdl.org \
--cc=zwane@holomorphy.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 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.