From: [email protected]
To: Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH net-next 0/2] minor tcp io_uring zc optimisations
Date: Wed, 17 May 2023 07:40:20 +0000 [thread overview]
Message-ID: <168430922098.967.17125641782139822162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <[email protected]>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <[email protected]>:
On Mon, 15 May 2023 17:06:35 +0100 you wrote:
> Patch 1 is a simple cleanup, patch 2 gives removes 2 atomics from the
> io_uring zc TCP submission path, which yielded extra 0.5% for my
> throughput CPU bound tests based on liburing/examples/send-zerocopy.c
>
> Pavel Begunkov (2):
> net/tcp: don't peek at tail for io_uring zc
> net/tcp: optimise io_uring zc ubuf refcounting
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/tcp: don't peek at tail for io_uring zc
https://git.kernel.org/netdev/net-next/c/eea96a3e2c90
- [net-next,2/2] net/tcp: optimise io_uring zc ubuf refcounting
https://git.kernel.org/netdev/net-next/c/a7533584728d
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:[~2023-05-17 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 16:06 [PATCH net-next 0/2] minor tcp io_uring zc optimisations Pavel Begunkov
2023-05-15 16:06 ` [PATCH net-next 1/2] net/tcp: don't peek at tail for io_uring zc Pavel Begunkov
2023-05-15 17:27 ` David Ahern
2023-05-15 18:11 ` Eric Dumazet
2023-05-15 16:06 ` [PATCH net-next 2/2] net/tcp: optimise io_uring zc ubuf refcounting Pavel Begunkov
2023-05-15 17:29 ` David Ahern
2023-05-15 18:14 ` Eric Dumazet
2023-05-15 18:40 ` David Ahern
2023-05-16 12:59 ` Pavel Begunkov
2023-05-16 14:37 ` David Ahern
2023-05-16 17:46 ` Pavel Begunkov
2023-05-17 7:40 ` 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=168430922098.967.17125641782139822162.git-patchwork-notify@kernel.org \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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