From: Andrew Morton <akpm@osdl.org>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org,
ashok.raj@intel.com, suresh.b.siddha@intel.com,
rajesh.shah@intel.com
Subject: Re: More than 8 CPUs detected and CONFIG_X86_PC cannot handle it on 2.6.16-rc6
Date: Sun, 12 Mar 2006 14:30:53 -0800 [thread overview]
Message-ID: <20060312143053.530ef6c9.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603122206110.19689@bizon.gios.gov.pl>
Krzysztof Oledzki <olel@ans.pl> wrote:
>
> > Actually, this warning should be seen on many other systems on well. We
> > use the bigsmp when there _or_ more than 8 CPUs or CPU_HOTPLUG is used.
> > So, in that sense the message is wrong, it should also have CPU_HOTPLUG in
> > there. Or we should make CPU_HOTPLUG depend on GENERIC_ARCH or auto select
> > GENERIC_ARCH with hotplug at the CONFIG level.
>
> Why? I have exactly 4 HT CPUs (2 cores), no more. I use CPU hotplug so I
> can disable or enable any of them when I want to. So, this is a classic
> SMP system and 2.6.15 is totally happy with this. Or is there any other
> (better?) way to disable/enable CPU (especially second logical CPU from
> HT) on running systems?
Maybe we should have:
if (num_possible_cpus() <= 8)
dont_do_any_of_that_stuff();
That's assuming that hotplug-cpu-capable platforms are correctly setting
cpu_possible_map. Do they?
next prev parent reply other threads:[~2006-03-12 22:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 2:04 Krzysztof Oledzki
2006-03-12 5:03 ` Andrew Morton
2006-03-12 11:04 ` Krzysztof Oledzki
2006-03-12 11:25 ` Andrew Morton
2006-03-12 13:05 ` Krzysztof Oledzki
2006-03-12 15:35 ` Venkatesh Pallipadi
2006-03-12 21:13 ` Krzysztof Oledzki
2006-03-12 22:30 ` Andrew Morton [this message]
2006-03-13 19:36 ` Ashok Raj
2006-03-13 19:51 ` Andrew Morton
2006-03-13 20:05 ` Ashok Raj
2006-03-13 22:22 ` Andrew Morton
2006-03-13 23:04 ` Ashok Raj
2006-03-15 5:44 ` Nathan Lynch
2006-03-15 6:18 ` Shaohua Li
2006-03-15 7:31 ` Andrew Morton
2006-03-15 9:37 ` [PATCH] No need to protect current->group_info in sys_getgroups(), in_group_p() and in_egroup_p() Eric Dumazet
2006-03-20 19:09 ` [PATCH] Use unsigned int types for a faster bsearch Eric Dumazet
2006-03-22 5:06 ` [PATCH] Use __read_mostly on some hot fs variables Eric Dumazet
2006-03-22 5:15 ` Nick Piggin
2006-03-22 6:23 ` [RFC, PATCH] avoid some atomics in open()/close() for monothreaded processes Eric Dumazet
2006-03-22 6:41 ` Andrew Morton
2006-03-22 6:59 ` Eric Dumazet
2006-03-22 7:03 ` Andrew Morton
2006-03-15 18:09 ` More than 8 CPUs detected and CONFIG_X86_PC cannot handle it on 2.6.16-rc6 Ashok Raj
2006-03-15 10:50 Chuck Ebbert
2006-03-15 15:44 ` Krzysztof Oledzki
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=20060312143053.530ef6c9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olel@ans.pl \
--cc=rajesh.shah@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@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
all inboxes | Powered by JetHome®