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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 27 Oct 2010 16:24:21 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Tejun Heo <tj@...nel.org>
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

Le mercredi 27 octobre 2010 à 16:00 +0200, Tejun Heo a écrit :

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

Yes this is the same

32bit : # numactl --hardware
available: 2 nodes (0-1)
node 0 cpus: 1 3 5 7 9 11 13 15
node 0 size: 2047 MB
node 0 free: 144 MB
node 1 cpus: 0 2 4 6 8 10 12 14
node 1 size: 2038 MB
node 1 free: 197 MB
node distances:
node   0   1 
  0:  10  20 
  1:  20  10 


64bit : # numactl --hardware
available: 2 nodes (0-1)
node 0 cpus: 1 3 5 7 9 11 13 15
node 0 size: 2047 MB
node 0 free: 1868 MB
node 1 cpus: 0 2 4 6 8 10 12 14
node 1 size: 2038 MB
node 1 free: 1912 MB
node distances:
node   0   1 
  0:  10  20 
  1:  20  10 
# cat /proc/buddyinfo 
Node 0, zone      DMA      1      0      1      0      2      1      1      0      1      1      3 
Node 0, zone    DMA32    454    206     93     15      3      1      1      2      1      3    460 
Node 1, zone    DMA32      3     19     17      1      0      1      1      1      1      1    380 
Node 1, zone   Normal     89     67     15      6      0      2      2      0      0      3     95 


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ