linux-kernel - Re: [PATCH] x86-32: Allocate irq stacks seperate from percpu area

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CC83067.5000009@kernel.org>
Date:	Wed, 27 Oct 2010 16:00:07 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Brian Gerst <brgerst@...il.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	mingo@...e.hu
Subject: Re: [PATCH] x86-32: Allocate irq stacks seperate from percpu area

On 10/27/2010 03:57 PM, Eric Dumazet wrote:
>> What does cpu_to_node() on each cpu say?  Also, do you know why
>> num_possible_cpus() is 32, not 16?
>>
> 
> I dont know, machine is HP ProLiant BL460c G6 
> [    0.000000] SMP: Allowing 32 CPUs, 16 hotplug CPUs
> 
> for_each_possible_cpu(cpu) {
> 	pr_err("cpu=%d node=%d\n", cpu, cpu_to_node(cpu));
> }
> 
> cpu=0 node=1
> cpu=1 node=0
> cpu=2 node=1
> cpu=3 node=0
> cpu=4 node=1
> cpu=5 node=0
> cpu=6 node=1
> cpu=7 node=0
> cpu=8 node=1
> cpu=9 node=0
> cpu=10 node=1
> cpu=11 node=0
> cpu=12 node=1
> cpu=13 node=0
> cpu=14 node=1
> cpu=15 node=0
> cpu=16 node=0
> cpu=17 node=0
> cpu=18 node=0
> cpu=19 node=0
> cpu=20 node=0
> cpu=21 node=0
> cpu=22 node=0
> cpu=23 node=0
> cpu=24 node=0
> cpu=25 node=0
> cpu=26 node=0
> cpu=27 node=0
> cpu=28 node=0
> cpu=29 node=0
> cpu=30 node=0
> cpu=31 node=0

Heh, interesting table.  What does the same code say on 64bit?  Is it
the same?

-- 
tejun
--
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/