Commit 64f26e5c authored by Paul E. McKenney's avatar Paul E. McKenney

kthread: Add pointer to vmstat-avoidance patch

Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: default avatarJosh Triplett <josh@joshtriplett.org>
parent 64d3b7a1
...@@ -181,12 +181,17 @@ To reduce its OS jitter, do any of the following: ...@@ -181,12 +181,17 @@ To reduce its OS jitter, do any of the following:
make sure that this is safe on your particular system. make sure that this is safe on your particular system.
d. It is not possible to entirely get rid of OS jitter d. It is not possible to entirely get rid of OS jitter
from vmstat_update() on CONFIG_SMP=y systems, but you from vmstat_update() on CONFIG_SMP=y systems, but you
can decrease its frequency by writing a large value to can decrease its frequency by writing a large value
/proc/sys/vm/stat_interval. The default value is HZ, to /proc/sys/vm/stat_interval. The default value is
for an interval of one second. Of course, larger values HZ, for an interval of one second. Of course, larger
will make your virtual-memory statistics update more values will make your virtual-memory statistics update
slowly. Of course, you can also run your workload at more slowly. Of course, you can also run your workload
a real-time priority, thus preempting vmstat_update(). at a real-time priority, thus preempting vmstat_update(),
but if your workload is CPU-bound, this is a bad idea.
However, there is an RFC patch from Christoph Lameter
(based on an earlier one from Gilad Ben-Yossef) that
reduces or even eliminates vmstat overhead for some
workloads at https://lkml.org/lkml/2013/9/4/379.
e. If running on high-end powerpc servers, build with e. If running on high-end powerpc servers, build with
CONFIG_PPC_RTAS_DAEMON=n. This prevents the RTAS CONFIG_PPC_RTAS_DAEMON=n. This prevents the RTAS
daemon from running on each CPU every second or so. daemon from running on each CPU every second or so.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment