Skip to main content

Browse the archive

Revision dac876193cd79ced36d0462749ea47c05844fb49 authored by Terry Loftin on 09 April 2010, 10:29:49 UTC, committed by David S. Miller on 13 April 2010, 10:03:13 UTC 
e1000e: stop cleaning when we reach tx_ring->next_to_use
 
Tx ring buffers after tx_ring->next_to_use are volatile and could
change, possibly causing a crash.  Stop cleaning when we hit
tx_ring->next_to_use.

Signed-off-by: Terry Loftin <terry.loftin@hp.com>
Acked-by: Bruce Allan <bruce.w.allan@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent d5aa225
Raw File
numastat.txt 

Numa policy hit/miss statistics

/sys/devices/system/node/node*/numastat

All units are pages. Hugepages have separate counters.

numa_hit			A process wanted to allocate memory from this node,
					and succeeded.
numa_miss			A process wanted to allocate memory from another node,
					but ended up with memory from this node.
numa_foreign		A process wanted to allocate on this node,
				    but ended up with memory from another one.
local_node			A process ran on this node and got memory from it.
other_node			A process ran on this node and got memory from another node.
interleave_hit 		Interleaving wanted to allocate from this node
					and succeeded.

For easier reading you can use the numastat utility from the numactl package
(ftp://ftp.suse.com/pub/people/ak/numa/numactl*). Note that it only works
well right now on machines with a small number of CPUs.
back to top