From: Jack Steiner <steiner@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: tglx@linutronix.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - Increase MAX_APICS for large configs
Date: Wed, 16 Apr 2008 14:22:38 -0500 [thread overview]
Message-ID: <20080416192238.GA12115@sgi.com> (raw)
In-Reply-To: <20080416184543.GD3722@elte.hu>
On Wed, Apr 16, 2008 at 08:45:43PM +0200, Ingo Molnar wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > Increase the maximum number of apics when running very large
> > configurations. This patch has no affect on most systems.
> >
> > Signed-off-by: Jack Steiner <steiner@sgi.com>
> >
> > I think this area of the code will be substantially changed when the
> > full x2apic patch is available. In the meantime, this seems like an
> > acceptible alternative. The patch has no effect on any 32-bit kernel.
> > It adds ~4k to the size of 64-bit kernels but only if NR_CPUS > 255.
>
> ugly ... but well - applied. What's the static size cost of 64K APICs?
64k APICs would add ~8k to the static size of the kernel. Most of the
increase is in the phys_cpu_present_map[].
When the x2apic patch is integrated, I expect (may be wrong) that this
array will be eliminated since x2apic increases the max APIC_ID to 32 bits,
Note that MAX_APICS is really misnamed. It is not the maximum number of APICs. It
is the value of the largest APIC ID. IDs are not necessarily dense.
--- jack
WARNING: multiple messages have this Message-ID (diff)
From: Jack Steiner <steiner@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: tglx@linutronix.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - Increase MAX_APICS for large configs
Date: Wed, 16 Apr 2008 14:22:38 -0500 [thread overview]
Message-ID: <20080416192238.GA12115@sgi.com> (raw)
In-Reply-To: <20080416184543.GD3722@elte.hu>
On Wed, Apr 16, 2008 at 08:45:43PM +0200, Ingo Molnar wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > Increase the maximum number of apics when running very large
> > configurations. This patch has no affect on most systems.
> >
> > Signed-off-by: Jack Steiner <steiner@sgi.com>
> >
> > I think this area of the code will be substantially changed when the
> > full x2apic patch is available. In the meantime, this seems like an
> > acceptible alternative. The patch has no effect on any 32-bit kernel.
> > It adds ~4k to the size of 64-bit kernels but only if NR_CPUS > 255.
>
> ugly ... but well - applied. What's the static size cost of 64K APICs?
64k APICs would add ~8k to the static size of the kernel. Most of the
increase is in the phys_cpu_present_map[].
When the x2apic patch is integrated, I expect (may be wrong) that this
array will be eliminated since x2apic increases the max APIC_ID to 32 bits,
Note that MAX_APICS is really misnamed. It is not the maximum number of APICs. It
is the value of the largest APIC ID. IDs are not necessarily dense.
--- jack
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-16 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 16:39 [PATCH] - Increase MAX_APICS for large configs Jack Steiner
2008-04-16 16:39 ` Jack Steiner
2008-04-16 18:45 ` Ingo Molnar
2008-04-16 18:45 ` Ingo Molnar
2008-04-16 19:22 ` Jack Steiner [this message]
2008-04-16 19:22 ` Jack Steiner
2008-04-17 11:07 ` Ingo Molnar
2008-04-17 11:07 ` Ingo Molnar
2008-04-17 18:02 ` Yinghai Lu
2008-04-17 18:02 ` Yinghai Lu
2008-04-18 21:14 ` Jack Steiner
2008-04-18 21:14 ` Jack Steiner
2008-04-18 22:01 ` Yinghai Lu
2008-04-18 22:01 ` Yinghai Lu
2008-04-19 0:01 ` Jack Steiner
2008-04-19 0:01 ` Jack Steiner
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=20080416192238.GA12115@sgi.com \
--to=steiner@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.