diff options
author | 2021-03-08 08:51:01 -0800 | |
---|---|---|
committer | 2021-03-08 08:52:45 -0800 | |
commit | bbb41728e61a602ec76cbfec2a49ccc763d305b7 (patch) | |
tree | af863fd112a199148f11c746556393b48d9029d7 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | selftests/bpf: Fix test_attach_probe for powerpc uprobes (diff) | |
parent | libbpf, xsk: Add libbpf_smp_store_release libbpf_smp_load_acquire (diff) | |
download | wireguard-linux-bbb41728e61a602ec76cbfec2a49ccc763d305b7.tar.xz wireguard-linux-bbb41728e61a602ec76cbfec2a49ccc763d305b7.zip |
Merge branch 'load-acquire/store-release barriers for'
Björn Töpel says:
====================
This two-patch series introduces load-acquire/store-release barriers
for the AF_XDP rings.
For most contemporary architectures, this is more effective than a
SPSC ring based on smp_{r,w,}mb() barriers. More importantly,
load-acquire/store-release semantics make the ring code easier to
follow.
This is effectively the change done in commit 6c43c091bdc5
("documentation: Update circular buffer for
load-acquire/store-release"), but for the AF_XDP rings.
Both libbpf and the kernel-side are updated.
Full details are outlined in the commits!
Thanks to the LKMM-folks (Paul/Alan/Will) for helping me out in this
complicated matter!
Changelog
v1[1]->v2:
* Expanded the commit message for patch 1, and included the LKMM
litmus tests. Hopefully this clear things up. (Daniel)
* Clarified why the smp_mb()/smp_load_acquire() is not needed in (A);
control dependency with load to store. (Toke)
[1] https://lore.kernel.org/bpf/20210301104318.263262-1-bjorn.topel@gmail.com/
Thanks,
Björn
====================
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions