7a2d19bced
When correlating ftrace results with /proc/vmstat, I noticed that the reporting scripts value for "pages scanned" differed significantly. Both values were "right" depending on how you look at it. The difference is due to vmstat only counting scanning of the inactive list towards pages scanned. The analysis script for the tracepoint counts active and inactive list yielding a far higher value than vmstat. The resulting scanning/reclaim ratio looks much worse. The tracepoint is ok but this patch updates the reporting script so that the report values for scanned are similar to vmstat. Signed-off-by: Mel Gorman <mel@csn.ul.ie> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| postprocess | ||
| events-kmem.txt | ||
| events.txt | ||
| ftrace-design.txt | ||
| ftrace.txt | ||
| function-graph-fold.vim | ||
| kprobetrace.txt | ||
| mmiotrace.txt | ||
| ring-buffer-design.txt | ||
| tracepoint-analysis.txt | ||
| tracepoints.txt | ||