You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* For more information about LTTng, [see its documentation](https://lttng.org/docs/v2.11/).
63
+
* For more information about LTTng, [see its documentation](https://lttng.org/docs/v2.13/).
64
64
2. Build:
65
65
* If you've already built ROS 2 from source before installing LTTng, you will need to re-build at least up to `tracetools`:
66
66
```
@@ -101,7 +101,7 @@ The tracing directory can be configured using command/launch action parameters,
101
101
* Use `$ROS_TRACE_DIR` if `ROS_TRACE_DIR` is set and not empty.
102
102
* Otherwise, use `$ROS_HOME/tracing`, using `~/.ros` for `ROS_HOME` if not set or if empty.
103
103
104
-
Additionally, **if you're using kernel tracing with a non-root user, make sure that the [`tracing` group exists and that your user is added to it](https://lttng.org/docs/v2.11/#doc-tracing-group)**.
104
+
Additionally, **if you're using kernel tracing with a non-root user, make sure that the [`tracing` group exists and that your user is added to it](https://lttng.org/docs/v2.13/#doc-tracing-group)**.
105
105
106
106
```
107
107
# Create group if it doesn't exist
@@ -134,7 +134,7 @@ This way, tracing automatically starts when launching the launch file and ends w
134
134
$ ros2 launch tracetools_launch example.launch.py
135
135
```
136
136
137
-
The `Trace` action will also set the `LD_PRELOAD` environment to preload [LTTng's userspace tracing helper(s)](https://lttng.org/docs/#doc-prebuilt-ust-helpers) if the corresponding event(s) are enabled.
137
+
The `Trace` action will also set the `LD_PRELOAD` environment to preload [LTTng's userspace tracing helper(s)](https://lttng.org/docs/v2.13/#doc-prebuilt-ust-helpers) if the corresponding event(s) are enabled.
138
138
For more information, see [this example launch file](./tracetools_launch/launch/example.launch.py) and the [`Trace` action](./tracetools_launch/tracetools_launch/action.py).
139
139
140
140
You must [install the kernel tracer](#building) if you want to enable kernel events (`events_kernel` in Python, `events-kernel` in XML or YAML).
@@ -156,9 +156,9 @@ It is a low-overhead tracer with many important real-time compatible features:
156
156
157
157
However, some settings need to be tuned for it to be fully real-time safe and for performance to be optimal for your use-case:
158
158
159
-
* timers[^rt-1]: use [read timer](https://lttng.org/docs/v2.11/#doc-channel-read-timer) to avoid a write(2) call
159
+
* timers[^rt-1]: use [read timer](https://lttng.org/docs/v2.13/#doc-channel-read-timer) to avoid a write(2) call
160
160
* sub-buffer[^rt-1] count and size:
161
-
* see [documentation](https://lttng.org/docs/v2.11/#doc-channel-subbuf-size-vs-subbuf-count) for sub-buffer count and size tuning tips based on your use-case
161
+
* see [documentation](https://lttng.org/docs/v2.13/#doc-channel-subbuf-size-vs-subbuf-count) for sub-buffer count and size tuning tips based on your use-case
162
162
* minimize sub-buffer count to minimize sub-buffer switching overhead
163
163
* one-time memory allocation/lock/syscall per thread:
164
164
* usually done the first time a tracepoint is executed within a thread for URCU thread registration, but registration can be manually performed to force it to be done during your application's initialization
@@ -168,7 +168,7 @@ However, some settings need to be tuned for it to be fully real-time safe and fo
* [Combined Tracing of the Kernel and Applications with LTTng](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.641.1965&rep=rep1&type=pdf#page=87): LTTng-UST architecture and design goals (section 3)
173
173
* [Survey and Analysis of Kernel and Userspace Tracers on Linux: Design, Implementation, and Overhead](https://dl.acm.org/doi/abs/10.1145/3158644): LTTng-UST overhead and design compared to other kernel and userspace tracers (table 6: average latency overhead per tracepoint of 158 ns)
0 commit comments