From: Ingo Molnar <mingo@elte.hu>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, ashok.raj@intel.com
Subject: Re: [patch] genapic: optimize & fix APIC mode setup
Date: Mon, 13 Nov 2006 20:04:52 +0100 [thread overview]
Message-ID: <20061113190452.GA29109@elte.hu> (raw)
In-Reply-To: <20061113103051.D17720@unix-os.sc.intel.com>
* Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:
> On Mon, Nov 13, 2006 at 07:42:56PM +0100, Ingo Molnar wrote:
> > * Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:
> > > Not really. That chipset belongs to a MP platform and with your
> > > proposed patch, we will endup using clustered APIC mode and will hit
> > > the issue(in the presence of cpu hotplug) mentioned in that URL.
> >
> > hm, why does it end up in clustered mode? Cluster mode should only
> > trigger if the APIC IDs go beyond 16.
>
> go beyond '8' not 16. With Dual-core+HT these MP platforms will have
> 16 logical cpus.
yes - then the APIC ids will go beyond 15.
> > but i'd be fine with never going into cluster mode, instead always
> > using physical flat mode when having more than 8 APICs (independent
> > of the presence of CPU hotplug). On small systems, logical flat mode
> > is what is the best-tested variant (it's also slightly faster).
>
> Ok.
ok, that's really good. Is there any 'weird' platform that you are aware
of that absolutely needs clustered APIC mode (because it has no physical
delivery mode or something)?
Ingo
next prev parent reply other threads:[~2006-11-13 19:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 15:14 [patch] genapic: optimize & fix APIC mode setup Ingo Molnar
2006-11-11 15:20 ` Andi Kleen
2006-11-11 15:27 ` Ingo Molnar
2006-11-11 15:39 ` Ingo Molnar
2006-11-13 1:50 ` Siddha, Suresh B
2006-11-13 2:32 ` Andi Kleen
2006-11-13 8:16 ` Ingo Molnar
2006-11-13 9:08 ` Andi Kleen
2006-11-13 14:05 ` Ingo Molnar
2006-11-13 14:29 ` Andi Kleen
2006-11-13 15:04 ` Ingo Molnar
2006-11-13 16:10 ` Andi Kleen
2006-11-13 16:32 ` Ingo Molnar
2006-11-13 18:03 ` Siddha, Suresh B
2006-11-13 18:42 ` Ingo Molnar
2006-11-13 18:30 ` Siddha, Suresh B
2006-11-13 19:04 ` Ingo Molnar [this message]
2006-11-13 18:58 ` Siddha, Suresh B
2006-11-13 19:31 ` Ashok Raj
2006-11-13 19:08 ` Ingo Molnar
2006-11-13 14:14 ` Ingo Molnar
2006-11-13 8:43 ` Ingo Molnar
2006-11-13 17:34 ` Siddha, Suresh B
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=20061113190452.GA29109@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.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