[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0910291159030.27732@chino.kir.corp.google.com>
Date: Thu, 29 Oct 2009 12:06:21 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Mike Travis <travis@....com>
cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Jack Steiner <steiner@....com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Yinghai Lu <yinghai@...nel.org>, Mel Gorman <mel@....ul.ie>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [patch] x86: reduce srat verbosity in the kernel log
On Thu, 29 Oct 2009, Mike Travis wrote:
> I believe the disjointed ranges came from the hyperthread cpus..? Which if
> true means there'll probably be as many distinct ranges as there are threads
> per core?
>
Not necessarily, look at the first few lines of your new output:
[ 0.000000] SRAT: PXM 0 -> APIC {0-7,16-23} -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC {32-39,48-55} -> Node 1
[ 0.000000] SRAT: PXM 2 -> APIC {64-71,80-87} -> Node 2
...
If those values are in hex, you have these apic id ranges:
0x00-0x07, 0x10-0x17
0x20-0x27, 0x30-0x37
0x40-0x47, 0x50-0x57
...
So it's most likely that each of the physical processors has eight logical
processors (represented by the least significant three bits) and there are
two physical processors (the more significant four bits) per node.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists