diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2026-08-13 15:05:04 +0200 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2026-08-13 15:05:05 +0200 |
| commit | 3205699d79f262412c1be7fc1c04066610d3cd52 (patch) | |
| tree | a1e0487449723c29c85b7be98410cffa6a2fc0f4 /tools/perf/scripts/python/libxed.py | |
| parent | 885a48b521b40aa515ad47f5581535b5763d105c (diff) | |
| parent | 3d2452c2fb2fe37d8b1eb5b814561e71eb8652f3 (diff) | |
Merge branch 'netconsole-replace-target_list_lock-by-rcu-on-userdata-hot-path'
Breno Leitao says:
====================
netconsole: replace target_list_lock by RCU on userdata hot path
I would like to move netconsole to use RCU on the hot path for
a while instead of target_list_lock. My goal is to have no lock on the
tx side at all and eventually drop CON_NBCON_ATOMIC_UNSAFE, if that is
possible [1].
Start removing target_list_lock on certain parts of the code. This patch
transforms the userdata array into a RCU-protected pointer, and uses the
dynamic mutex as the write lock.
Added a selftest, given we didn't have any netconsole selftest for
userdata operations. Feel free to drop it if this is not useful, dear
maintainers.
Link: https://lore.kernel.org/all/20251121-nbcon-v1-0-503d17b2b4af@debian.org/[1]
Signed-off-by: Breno Leitao <leitao@debian.org>
====================
Link: https://patch.msgid.link/20260810-netcons-userdata-rcu-v3-0-f65557f769ce@debian.org
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions
