Thread (8 messages) flat view 8 messages, 3 authors, 2025-09-02

Re: [PATCH net-next v10 1/2] net: af_packet: remove last_kactive_blk_num field

From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: 2025-09-01 01:18:10
Also in: lkml

Xin Zhao wrote:
kactive_blk_num (K) is incremented on block close. last_kactive_blk_num (L)
is set to match K on block open and each timer. So the only time that they
differ is if a block is closed in tpacket_rcv and no new block could be
opened.
So the origin check L==K in timer callback only skip the case 'no new block
to open'. If we remove L==K check, it will make prb_curr_blk_in_use check
earlier, which will not cause any side effect.

Signed-off-by: Xin Zhao <redacted>
Reviewed-by: Willem de Bruijn <willemb@google.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