From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Dave Jones <davej@redhat.com>, YhLu <YhLu@tyan.com>,
Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way
Date: Fri, 3 Jun 2005 12:26:41 -0700 [thread overview]
Message-ID: <20050603122641.A31139@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050602190350.GD18775@redhat.com>; from davej@redhat.com on Thu, Jun 02, 2005 at 03:03:50PM -0400
On Thu, Jun 02, 2005 at 03:03:50PM -0400, Dave Jones wrote:
> On Thu, Jun 02, 2005 at 11:56:25AM -0700, YhLu wrote:
> > Really?, smp_num_siblings is global variable and initially is set 1.
>
> Why shouldn't it be ? It would only make sense to make it
> non-global if we supported a configuration where different
> CPUs had different numbers of siblings, which we don't.
> (And I'm fairly sure that AMD/Intel don't/won't either)
It will help if someone uses "maxcpus" boot param or if someone
wants to disable/enable certain logical siblings using HOTPLUG.
That is conceptually more cleaner too. Will do it post 2.6.12.
thanks,
suresh
next prev parent reply other threads:[~2005-06-03 19:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 18:56 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way YhLu
2005-06-02 19:03 ` Dave Jones
2005-06-03 19:26 ` Siddha, Suresh B [this message]
2005-06-02 19:06 ` Ashok Raj
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 21:34 YhLu
2005-06-02 21:33 YhLu
2005-06-03 16:12 ` Andi Kleen
2005-06-02 21:15 YhLu
2005-06-02 20:42 YhLu
2005-06-03 16:09 ` Andi Kleen
2005-06-03 18:56 ` Siddha, Suresh B
2005-06-02 18:55 YhLu
2005-06-02 3:26 YhLu
2005-06-02 18:51 ` Andi Kleen
2005-06-02 3:16 YhLu
2005-06-02 18:50 ` Andi Kleen
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=20050603122641.A31139@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=YhLu@tyan.com \
--cc=ak@muc.de \
--cc=davej@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox