From: "David S. Miller" <davem@davemloft.net>
To: davej@redhat.com
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: for_each_online_cpu broken ?
Date: Wed, 07 Dec 2005 21:38:25 -0800 (PST) [thread overview]
Message-ID: <20051207.213825.27890558.davem@davemloft.net> (raw)
In-Reply-To: <20051208053302.GA28201@redhat.com>
From: Dave Jones <davej@redhat.com>
Date: Thu, 8 Dec 2005 00:33:02 -0500
> On Thu, Dec 08, 2005 at 06:26:32AM +0100, Andi Kleen wrote:
>
> > The possible map is fixed kind of BTW in 2.6.15rc*. It was a side effect
> > of CPU hotplug, which now uses a better algorithm to guess the
> > number of possible CPUs. In 2.6.15 you will just get half the number
> > of available CPUs in addition by default
>
> Yep, I noticed it offers a maximum of 6 cpus on my way.
> As a sidenote, seems kinda funny (and wasteful maybe?), doing this
> on a lot of hardware that isn't hotplug capable. (Whilst I could
> disable cpu hotplug in my local build, this isn't an answer for
> a generic distro kernel).
This can be dangerous btw, as some subsystem such as netfilter
allocate enormous datastructures based upon the largest possible
cpu number in the system.
In 2.6.16 it will use something a bit more intelligent, but
overestimating the possible cpu set can be quite a waste.
next prev parent reply other threads:[~2005-12-08 5:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 5:07 Dave Jones
2005-12-08 5:26 ` Andi Kleen
2005-12-08 5:33 ` Dave Jones
2005-12-08 5:38 ` David S. Miller [this message]
2005-12-08 6:12 ` Andi Kleen
2005-12-08 6:27 ` Dave Jones
2005-12-08 6:22 ` Nigel Cunningham
2005-12-08 6:28 ` Dave Jones
2005-12-08 6:30 ` Andi Kleen
2005-12-09 0:03 ` Nigel Cunningham
2005-12-08 6:30 ` Andi Kleen
2005-12-08 6:43 ` Dave Jones
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=20051207.213825.27890558.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.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
Powered by JetHome