From: Martin KaFai Lau <martin.lau@linux.dev>
To: Jordan Rife <jordan@jrife.io>
Cc: Aditi Ghag <aditi.ghag@isovalent.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v7 bpf-next 5/7] bpf: udp: Avoid socket skips and repeats during iteration
Date: Fri, 2 May 2025 14:29:04 -0700 [thread overview]
Message-ID: <1aff3b57-d125-4ca4-b56a-e47ff1de6094@linux.dev> (raw)
In-Reply-To: <20250502161528.264630-6-jordan@jrife.io>
On 5/2/25 9:15 AM, Jordan Rife wrote:
> static struct sock *bpf_iter_udp_batch(struct seq_file *seq)
> {
> struct bpf_udp_iter_state *iter = seq->private;
> struct udp_iter_state *state = &iter->state;
> + unsigned int find_cookie, end_cookie = 0;
A nit. I removed the zero initialization in the "end_cookie". Like
"find_cookie", both of them will be initialized by iter->cur_sk and iter->end_sk
later.
Applied. Thanks.
> struct net *net = seq_file_net(seq);
> - int resume_bucket, resume_offset;
> struct udp_table *udptable;
> unsigned int batch_sks = 0;
> + int resume_bucket;
> int resizes = 0;
> struct sock *sk;
> int err = 0;
>
> resume_bucket = state->bucket;
> - resume_offset = iter->offset;
>
> /* The current batch is done, so advance the bucket. */
> if (iter->cur_sk == iter->end_sk)
> @@ -3434,6 +3452,8 @@ static struct sock *bpf_iter_udp_batch(struct seq_file *seq)
> * before releasing the bucket lock. This allows BPF programs that are
> * called in seq_show to acquire the bucket lock if needed.
> */
> + find_cookie = iter->cur_sk;
> + end_cookie = iter->end_sk;
> iter->cur_sk = 0;
> iter->end_sk = 0;
> batch_sks = 0;
next prev parent reply other threads:[~2025-05-02 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 16:15 [PATCH v7 bpf-next 0/7] bpf: udp: Exactly-once socket iteration Jordan Rife
2025-05-02 16:15 ` [PATCH v7 bpf-next 1/7] bpf: udp: Make mem flags configurable through bpf_iter_udp_realloc_batch Jordan Rife
2025-05-02 21:31 ` Martin KaFai Lau
2025-05-02 16:15 ` [PATCH v7 bpf-next 2/7] bpf: udp: Make sure iter->batch always contains a full bucket snapshot Jordan Rife
2025-05-02 16:15 ` [PATCH v7 bpf-next 3/7] bpf: udp: Get rid of st_bucket_done Jordan Rife
2025-05-02 16:15 ` [PATCH v7 bpf-next 4/7] bpf: udp: Use bpf_udp_iter_batch_item for bpf_udp_iter_state batch items Jordan Rife
2025-05-02 21:22 ` Martin KaFai Lau
2025-05-02 21:31 ` Jordan Rife
2025-05-02 16:15 ` [PATCH v7 bpf-next 5/7] bpf: udp: Avoid socket skips and repeats during iteration Jordan Rife
2025-05-02 21:29 ` Martin KaFai Lau [this message]
2025-05-02 16:15 ` [PATCH v7 bpf-next 6/7] selftests/bpf: Return socket cookies from sock_iter_batch progs Jordan Rife
2025-05-02 16:15 ` [PATCH v7 bpf-next 7/7] selftests/bpf: Add tests for bucket resume logic in UDP socket iterators Jordan Rife
2025-05-02 21:20 ` [PATCH v7 bpf-next 0/7] bpf: udp: Exactly-once socket iteration patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1aff3b57-d125-4ca4-b56a-e47ff1de6094@linux.dev \
--to=martin.lau@linux.dev \
--cc=aditi.ghag@isovalent.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jordan@jrife.io \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).