diff options
| author | Minchan Kim <minchan.kim@gmail.com> | 2009-09-21 17:03:21 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-09-22 07:17:39 -0700 |
| commit | 5d3bc2709114b416cab588c577e02c2470e40a6c (patch) | |
| tree | 155d04471863539a03cf94376f6b03f78f9daf16 /mm/mlock.c | |
| parent | a6f9edd65beaef24836e8934c8912c1e974dd45c (diff) | |
| download | kernel-common-5d3bc2709114b416cab588c577e02c2470e40a6c.tar.gz kernel-common-5d3bc2709114b416cab588c577e02c2470e40a6c.tar.bz2 kernel-common-5d3bc2709114b416cab588c577e02c2470e40a6c.zip | |
mm: fix NUMA accounting in numastat.txt
In Documentation/numastat.txt, it confused me. For example, there are
nodes [0,1] in system.
barrios:~$ cat /proc/zoneinfo | egrep 'numa|zone'
Node 0, zone DMA
numa_hit 33226
numa_miss 1739
numa_foreign 27978
..
..
Node 1, zone DMA
numa_hit 307
numa_miss 46900
numa_foreign 0
1) In node 0, NUMA_MISS means it wanted to allocate page
in node 1 but ended up with page in node 0
2) In node 0, NUMA_FOREIGN means it wanted to allocate page
in node 0 but ended up with page from Node 1.
But now, numastat explains it oppositely about (MISS, FOREIGN).
Let's fix up with viewpoint of zone.
Signed-off-by: Minchan Kim <minchan.kim@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Acked-by: Christoph Lameter <cl@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/mlock.c')
0 files changed, 0 insertions, 0 deletions