From: Bill Davidsen <davidsen@tmr.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Possible bug in 2.6.34 slub
Date: Mon, 31 May 2010 23:22:33 -0400 [thread overview]
Message-ID: <4C047CF9.9000804@tmr.com> (raw)
In-Reply-To: <20100531165528.35a323fb.rdunlap@xenotime.net>
Randy Dunlap wrote:
> On Tue, 1 Jun 2010 01:39:43 +0200 Giangiacomo Mariotti wrote:
>
>> Hi, I've recently noticed this line on the dmesg output(kernel 2.6.34):
>> [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0,
>> CPUs=16, Nodes=1
>>
>> My cpu is an I7 920, so it has 4 cores and there's hyperthreading
>> enabled, so there are 8 logical cpus. Is this a bug?
>
>
> No, it's just some boot/init time information.
>
I would consider it a bug to claim CPUs=xx when xx is something other than the
number of cores or the number of SMT threads supported by the processor. Of
course if /proc/cpuinfo shows four siblings per core or something exciting, then
it's right and you have a CPU you can sell to gizmodo and tell them a drunk left
on the bar.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2010-06-01 3:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 23:39 Possible bug in 2.6.34 slub Giangiacomo Mariotti
2010-05-31 23:55 ` Randy Dunlap
2010-06-01 3:22 ` Bill Davidsen [this message]
2010-06-01 19:17 ` Giangiacomo Mariotti
2010-06-01 19:39 ` Randy Dunlap
2010-06-01 19:48 ` Christoph Lameter
2010-06-01 21:11 ` Giangiacomo Mariotti
2010-06-01 21:27 ` Christoph Lameter
2010-06-03 6:51 ` Pekka Enberg
2010-06-03 13:34 ` Christoph Lameter
2010-06-04 18:39 ` Giangiacomo Mariotti
2010-06-07 22:35 ` Christoph Lameter
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=4C047CF9.9000804@tmr.com \
--to=davidsen@tmr.com \
--cc=gg.mariotti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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