From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: io-uring@vger.kernel.org, netdev@vger.kernel.org,
axboe@kernel.dk, davem@davemloft.net, kuba@kernel.org,
dsahern@kernel.org, edumazet@google.com,
willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net-next 0/5] zerocopy tx cleanups
Date: Tue, 02 Jul 2024 10:30:29 +0000 [thread overview]
Message-ID: <171991622986.11853.7798454667700291727.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1719190216.git.asml.silence@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 27 Jun 2024 13:59:40 +0100 you wrote:
> Assorted zerocopy send path cleanups, the main part of which is
> moving some net stack specific accounting out of io_uring back
> to net/ in Patch 4.
>
> Pavel Begunkov (5):
> net: always try to set ubuf in skb_zerocopy_iter_stream
> net: split __zerocopy_sg_from_iter()
> net: batch zerocopy_fill_skb_from_iter accounting
> io_uring/net: move charging socket out of zc io_uring
> net: limit scope of a skb_zerocopy_iter_stream var
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: always try to set ubuf in skb_zerocopy_iter_stream
https://git.kernel.org/netdev/net-next/c/9e2db9d3993e
- [net-next,2/5] net: split __zerocopy_sg_from_iter()
https://git.kernel.org/netdev/net-next/c/7fb05423fed4
- [net-next,3/5] net: batch zerocopy_fill_skb_from_iter accounting
https://git.kernel.org/netdev/net-next/c/aeb320fc05c7
- [net-next,4/5] io_uring/net: move charging socket out of zc io_uring
https://git.kernel.org/netdev/net-next/c/060f4ba6e403
- [net-next,5/5] net: limit scope of a skb_zerocopy_iter_stream var
https://git.kernel.org/netdev/net-next/c/2ca58ed21cef
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:[~2024-07-02 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 12:59 [PATCH net-next 0/5] zerocopy tx cleanups Pavel Begunkov
2024-06-27 12:59 ` [PATCH net-next 1/5] net: always try to set ubuf in skb_zerocopy_iter_stream Pavel Begunkov
2024-06-28 17:03 ` Willem de Bruijn
2024-06-27 12:59 ` [PATCH net-next 2/5] net: split __zerocopy_sg_from_iter() Pavel Begunkov
2024-06-28 17:03 ` Willem de Bruijn
2024-06-27 12:59 ` [PATCH net-next 3/5] net: batch zerocopy_fill_skb_from_iter accounting Pavel Begunkov
2024-06-28 17:06 ` Willem de Bruijn
2024-07-01 11:11 ` Pavel Begunkov
2024-07-01 18:27 ` Willem de Bruijn
2024-06-27 12:59 ` [PATCH net-next 4/5] io_uring/net: move charging socket out of zc io_uring Pavel Begunkov
2024-06-28 17:06 ` Willem de Bruijn
2024-06-27 12:59 ` [PATCH net-next 5/5] net: limit scope of a skb_zerocopy_iter_stream var Pavel Begunkov
2024-06-28 17:07 ` Willem de Bruijn
2024-06-28 17:09 ` [PATCH net-next 0/5] zerocopy tx cleanups Jens Axboe
2024-07-02 10:30 ` 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=171991622986.11853.7798454667700291727.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--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).