perf lock contention: Clear lock addr after use
Subsystems (2)
Namhyung Kim
maintainerPATCH v2 1/2 perf lock contention: Clear lock addr after use
It checks the current lock to calculated the delta of contention time. The address is saved in the tstamp map which is allocated at begining of contention and released at end of contention.
But it's possible for bpf_map_delete_elem() to fail. In that case, the element in the tstamp map kept for the current lock and it makes the next contention for the same lock tracked incorrectly. Specificially the next contention begin will see the existing element for the task and it'd just return. Then the next contention end will see the element and calculate the time using the timestamp for the previous begin.
This can result in a large value for two small contentions happened from time to time. Let's clear the lock address so that it can be updated next time even if the bpf_map_delete_elem() failed.
--- tools/perf/util/bpf_skel/lock_contention.bpf.c | 4 ++++ 1 file changed, 4 insertions(+)
tools/perf/util/bpf_skel/lock_contention.bpf.c +4 -0
@@ -389,6 +389,7 @@ int contention_end(u64 *ctx) duration =bpf_ktime_get_ns () - pelem->timestamp;if ((__s64 )duration <0 ) { + pelem->lock =0 ;bpf_map_delete_elem (&tstamp, &pid);__sync_fetch_and_add (&time_fail,1 );return 0 ;
@@ -422,6 +423,7 @@ int contention_end(u64 *ctx) data =bpf_map_lookup_elem (&lock_stat, &key);if (!data) {if (data_map_full) { + pelem->lock =0 ;bpf_map_delete_elem (&tstamp, &pid);__sync_fetch_and_add (&data_fail,1 );return 0 ;
@@ -445,6 +447,7 @@ int contention_end(u64 *ctx) data_map_full =1 ;__sync_fetch_and_add (&data_fail,1 ); } + pelem->lock =0 ;bpf_map_delete_elem (&tstamp, &pid);return 0 ; }
@@ -458,6 +461,7 @@ int contention_end(u64 *ctx)if (data->min_time > duration) data->min_time = duration; + pelem->lock =0 ;bpf_map_delete_elem (&tstamp, &pid);return 0 ; }
Signature · 1 line
2.42.0.609.gbb76f46606-goog
Namhyung Kim
maintainerPATCH v2 2/2 perf lock contention: Check tstamp elem creation
To be more conservative, let's check the return value of bpf_map_update_elem() for the tstamp map for a task and change the flag to BPF_NOEXIST so that it cannot update any existing element.
--- tools/perf/util/bpf_skel/lock_contention.bpf.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
tools/perf/util/bpf_skel/lock_contention.bpf.c +5 -1
@@ -328,7 +328,11 @@ int contention_begin(u64 *ctx)if (pelem ==NULL ) {struct tstamp_data zero = {}; -bpf_map_update_elem (&tstamp, &pid, &zero,BPF_ANY ); +if (bpf_map_update_elem (&tstamp, &pid, &zero,BPF_NOEXIST ) <0 ) { +__sync_fetch_and_add (&task_fail,1 ); +return 0 ; + } + pelem =bpf_map_lookup_elem (&tstamp, &pid);if (pelem ==NULL ) {__sync_fetch_and_add (&task_fail,1 );
Signature · 1 line
2.42.0.609.gbb76f46606-goog