aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorDave Hansen <[email protected]>2014-04-03 14:48:19 -0700
committerLinus Torvalds <[email protected]>2014-04-03 16:21:04 -0700
commit5509a5d27b971a90b940e148ca9ca53312e4fa7a (patch)
treea05845240563a79deafc3350e6409c6b3058e0f2 /tools/perf/scripts/python/syscall-counts.py
parent67f9fd91f93c582b7de2ab9325b6e179db77e4d5 (diff)
drop_caches: add some documentation and info message
There is plenty of anecdotal evidence and a load of blog posts suggesting that using "drop_caches" periodically keeps your system running in "tip top shape". Perhaps adding some kernel documentation will increase the amount of accurate data on its use. If we are not shrinking caches effectively, then we have real bugs. Using drop_caches will simply mask the bugs and make them harder to find, but certainly does not fix them, nor is it an appropriate "workaround" to limit the size of the caches. On the contrary, there have been bug reports on issues that turned out to be misguided use of cache dropping. Dropping caches is a very drastic and disruptive operation that is good for debugging and running tests, but if it creates bug reports from production use, kernel developers should be aware of its use. Add a bit more documentation about it, a syslog message to track down abusers, and vmstat drop counters to help analyze problem reports. [[email protected]: checkpatch fixes] [[email protected]: add runtime suppression control] Signed-off-by: Dave Hansen <[email protected]> Signed-off-by: Michal Hocko <[email protected]> Acked-by: KOSAKI Motohiro <[email protected]> Acked-by: KAMEZAWA Hiroyuki <[email protected]> Signed-off-by: Johannes Weiner <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions