Re: [PATCH bpf] selftests/bpf: work-around EBUSY errors from hashmap update/delete

On Tue, Dec 22, 2020 at 3:58 PM Song Liu wrote: > > > > > On Dec 22, 2020, at 11:53 AM, Andrii Nakryiko wrote: > > > > 20b6cc34ea74 ("bpf: Avoid hashtab deadlock with map_locked") introduced > > a possibility of getting EBUSY error on lock contention, which seems to > > happen > > very determini

Re: [PATCH bpf] selftests/bpf: work-around EBUSY errors from hashmap update/delete

> On Dec 22, 2020, at 11:53 AM, Andrii Nakryiko wrote: > > 20b6cc34ea74 ("bpf: Avoid hashtab deadlock with map_locked") introduced > a possibility of getting EBUSY error on lock contention, which seems to happen > very deterministically in test_maps when running 1024 threads on low-CPU > machi

[PATCH bpf] selftests/bpf: work-around EBUSY errors from hashmap update/delete

20b6cc34ea74 ("bpf: Avoid hashtab deadlock with map_locked") introduced a possibility of getting EBUSY error on lock contention, which seems to happen very deterministically in test_maps when running 1024 threads on low-CPU machine. In libbpf CI case, it's a 2 CPU VM and it's hitting this 100% of t