diff options
| author |   Mateusz Guzik <mjguzik@gmail.com> | 2024-08-06 19:28:46 +0200 |
|---|---|---|
| committer |   Christian Brauner <brauner@kernel.org> | 2024-08-30 08:22:33 +0200 |
| commit | 087adb4f0f91ee330446a70af899e6a996e5cc13 (patch) | |
| tree | e087a606f59ceef5add818265921dea4f587c7de /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | file: remove outdated comment after close_fd() (diff) | |
| download | wireguard-linux-087adb4f0f91ee330446a70af899e6a996e5cc13.tar.xz wireguard-linux-087adb4f0f91ee330446a70af899e6a996e5cc13.zip | |
vfs: dodge smp_mb in break_lease and break_deleg in the common case
These inlines show up in the fast path (e.g., in do_dentry_open()) and
induce said full barrier regarding i_flctx access when in most cases the
pointer is NULL.
The pointer can be safely checked before issuing the barrier, dodging it
in most cases as a result.
It is plausible the consume fence would be sufficient, but I don't want
to go audit all callers regarding what they before calling here.
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Link: https://lore.kernel.org/r/20240806172846.886570-1-mjguzik@gmail.com
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions