22 Sep, 2009
1 commit
-
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 01) In node 0, NUMA_MISS means it wanted to allocate page
in node 1 but ended up with page in node 02) 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
Cc: KAMEZAWA Hiroyuki
Acked-by: Christoph Lameter
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!