From: patchwork-bot+netdevbpf@kernel.org
To: Feng Yang <yangfeng59949@163.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, willemb@google.com,
almasrymina@google.com, kerneljasonxing@gmail.com,
ebiggers@google.com, asml.silence@gmail.com,
aleksander.lobakin@intel.com, stfomichev@gmail.com,
david.laight.linux@gmail.com, yangfeng@kylinos.cn,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] skbuff: Add MSG_MORE flag to optimize tcp large packet transmission
Date: Thu, 10 Jul 2025 02:40:14 +0000 [thread overview]
Message-ID: <175211521451.965283.8119309405484666271.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708054053.39551-1-yangfeng59949@163.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Jul 2025 13:40:53 +0800 you wrote:
> From: Feng Yang <yangfeng@kylinos.cn>
>
> When using sockmap for forwarding, the average latency for different packet sizes
> after sending 10,000 packets is as follows:
> size old(us) new(us)
> 512 56 55
> 1472 58 58
> 1600 106 81
> 3000 145 105
> 5000 182 125
>
> [...]
Here is the summary with links:
- [v4] skbuff: Add MSG_MORE flag to optimize tcp large packet transmission
https://git.kernel.org/netdev/net-next/c/76d727ae02b5
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-07-10 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:40 Feng Yang
2025-07-08 7:02 ` Eric Dumazet
2025-07-10 2: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=175211521451.965283.8119309405484666271.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=willemb@google.com \
--cc=yangfeng59949@163.com \
--cc=yangfeng@kylinos.cn \
/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
all inboxes | Powered by JetHome®