From: Randy Dunlap <rdunlap@xenotime.net>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Possible bug in 2.6.34 slub
Date: Tue, 1 Jun 2010 12:39:59 -0700 [thread overview]
Message-ID: <20100601123959.747228c6.rdunlap@xenotime.net> (raw)
In-Reply-To: <AANLkTilLq-hn59CBcLnOsnT37ZizQR6MrZX6btKPhfpb@mail.gmail.com>
On Tue, 1 Jun 2010 21:17:40 +0200 Giangiacomo Mariotti wrote:
> On Tue, Jun 1, 2010 at 5:22 AM, Bill Davidsen <davidsen@tmr.com> wrote:
> > 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.
> >
> So....is it a bug or not?
Sorry, I think that I misread your report.
It does look like misinformation.
Let's cc Christoph Lameter & Pekka.
> The point is, I guess(didn't actually look at the code), if that's
> just the count of MAX number of cpus supported, which is a config time
> define and then the actual count gets refined afterwards by slub
> too(because I know that the rest of the kernel knows I've got 4
> cores/8 logical cpus) or not. Is that it? If this is not the case(that
> is, it's not a static define used as a MAX value), then I can't see
> what kind of boot/init time info it is. If it's a boot-time info, it
> just means it's a _wrong_ boot-time info.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2010-06-01 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimEFy6VM3InWlqhVooQjKGSD3yBxlgeRbQC2r1L@mail.gmail.com>
[not found] ` <20100531165528.35a323fb.rdunlap@xenotime.net>
[not found] ` <4C047CF9.9000804@tmr.com>
[not found] ` <AANLkTilLq-hn59CBcLnOsnT37ZizQR6MrZX6btKPhfpb@mail.gmail.com>
2010-06-01 19:39 ` Randy Dunlap [this message]
2010-06-01 19:48 ` Possible bug in 2.6.34 slub 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=20100601123959.747228c6.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=cl@linux-foundation.org \
--cc=davidsen@tmr.com \
--cc=gg.mariotti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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;
as well as URLs for NNTP newsgroup(s).