2.8, 2.0: add link to channel-switch-timer
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Wed, 15 Mar 2017 00:16:59 +0000 (20:16 -0400)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Wed, 15 Mar 2017 00:16:59 +0000 (20:16 -0400)
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
2.8/lttng-docs-2.8.txt
2.9/lttng-docs-2.9.txt

index f69a074603b7dd6d1893068928bdbf66a186f50a..9ff38988821008896ba057b03af3534169e69e32 100644 (file)
@@ -1558,8 +1558,8 @@ to configure the sub-buffer count and size for them:
 * **High event throughput**: In general, prefer bigger sub-buffers to
   lower the risk of losing event records.
 +
-Having bigger sub-buffers also ensures a lower sub-buffer switching
-frequency.
+Having bigger sub-buffers also ensures a lower
+<<channel-switch-timer,sub-buffer switching frequency>>.
 +
 The number of sub-buffers is only meaningful if you create the channel
 in overwrite mode: in this case, if a sub-buffer overwrite happens, the
index 7eaf6364cbad569c7f6a998d37aa26cf495f3040..da60330d074d82e6f5d7adbf4be8197e2567a92c 100644 (file)
@@ -1499,8 +1499,8 @@ to configure the sub-buffer count and size for them:
 * **High event throughput**: In general, prefer bigger sub-buffers to
   lower the risk of losing event records.
 +
-Having bigger sub-buffers also ensures a lower sub-buffer switching
-frequency.
+Having bigger sub-buffers also ensures a lower
+<<channel-switch-timer,sub-buffer switching frequency>>.
 +
 The number of sub-buffers is only meaningful if you create the channel
 in overwrite mode: in this case, if a sub-buffer overwrite happens, the
This page took 0.027938 seconds and 4 git commands to generate.