Thread (30 messages) 30 messages, 3 authors, 2021-03-30

RE: [Patch bpf-next v7 02/13] skmsg: introduce a spinlock to protect ingress_msg

From: John Fastabend <john.fastabend@gmail.com>
Date: 2021-03-29 19:12:20
Also in: bpf

Cong Wang wrote:
From: Cong Wang <redacted>

Currently we rely on lock_sock to protect ingress_msg,
it is too big for this, we can actually just use a spinlock
to protect this list like protecting other skb queues.

__tcp_bpf_recvmsg() is still special because of peeking,
it still has to use lock_sock.

Cc: John Fastabend <john.fastabend@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Lorenz Bauer <redacted>
Acked-by: Jakub Sitnicki <jakub@cloudflare.com>
Signed-off-by: Cong Wang <redacted>
---
Acked-by: John Fastabend <john.fastabend@gmail.com>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help