From: patchwork-bot+netdevbpf@kernel.org
To: Jordan Rife <jordan@jrife.io>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
aditi.ghag@isovalent.com, daniel@iogearbox.net,
martin.lau@linux.dev, willemdebruijn.kernel@gmail.com,
kuniyu@amazon.com, alexei.starovoitov@gmail.com
Subject: Re: [PATCH v7 bpf-next 0/7] bpf: udp: Exactly-once socket iteration
Date: Fri, 02 May 2025 21:20:38 +0000 [thread overview]
Message-ID: <174622083850.3731637.6479069584548815355.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250502161528.264630-1-jordan@jrife.io>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 2 May 2025 09:15:19 -0700 you wrote:
> Both UDP and TCP socket iterators use iter->offset to track progress
> through a bucket, which is a measure of the number of matching sockets
> from the current bucket that have been seen or processed by the
> iterator. On subsequent iterations, if the current bucket has
> unprocessed items, we skip at least iter->offset matching items in the
> bucket before adding any remaining items to the next batch. However,
> iter->offset isn't always an accurate measure of "things already seen"
> when the underlying bucket changes between reads which can lead to
> repeated or skipped sockets. Instead, this series remembers the cookies
> of the sockets we haven't seen yet in the current bucket and resumes
> from the first cookie in that list that we can find on the next
> iteration. This series focuses on UDP socket iterators, but a later
> series will apply a similar approach to TCP socket iterators.
>
> [...]
Here is the summary with links:
- [v7,bpf-next,1/7] bpf: udp: Make mem flags configurable through bpf_iter_udp_realloc_batch
(no matching commit)
- [v7,bpf-next,2/7] bpf: udp: Make sure iter->batch always contains a full bucket snapshot
https://git.kernel.org/bpf/bpf-next/c/66d454e99d71
- [v7,bpf-next,3/7] bpf: udp: Get rid of st_bucket_done
https://git.kernel.org/bpf/bpf-next/c/3fae8959cda5
- [v7,bpf-next,4/7] bpf: udp: Use bpf_udp_iter_batch_item for bpf_udp_iter_state batch items
(no matching commit)
- [v7,bpf-next,5/7] bpf: udp: Avoid socket skips and repeats during iteration
(no matching commit)
- [v7,bpf-next,6/7] selftests/bpf: Return socket cookies from sock_iter_batch progs
https://git.kernel.org/bpf/bpf-next/c/4a0614e18c2d
- [v7,bpf-next,7/7] selftests/bpf: Add tests for bucket resume logic in UDP socket iterators
https://git.kernel.org/bpf/bpf-next/c/c58dcc1dbe30
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-02 21:19 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
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 ` patchwork-bot+netdevbpf [this message]
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=174622083850.3731637.6479069584548815355.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=martin.lau@linux.dev \
--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