Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753693Ab0FATwX (ORCPT ); Tue, 1 Jun 2010 15:52:23 -0400 Received: from nlpi129.sbcis.sbc.com ([207.115.36.143]:56342 "EHLO nlpi129.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751762Ab0FATwW (ORCPT ); Tue, 1 Jun 2010 15:52:22 -0400 Date: Tue, 1 Jun 2010 14:48:58 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@router.home To: Randy Dunlap cc: Giangiacomo Mariotti , Pekka Enberg , Bill Davidsen , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: Possible bug in 2.6.34 slub In-Reply-To: <20100601123959.747228c6.rdunlap@xenotime.net> Message-ID: References: <20100531165528.35a323fb.rdunlap@xenotime.net> <4C047CF9.9000804@tmr.com> <20100601123959.747228c6.rdunlap@xenotime.net> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1578 Lines: 33 On Tue, 1 Jun 2010, Randy Dunlap wrote: > > >>> 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? Yes its a bug in the arch code or BIOS. The system configuration tells us that there are more possible cpus and therefore the system prepares for the additional cpus to be activated at some later time. > 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. No that is the max nr of cpus possible on this machine. The count is determined by hardware capabilities on bootup. If they are not detected in the right way then you have the erroneous display (and the system configures useless per cpu structures to support nonexistent cpus). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/