From: patchwork-bot+netdevbpf@kernel.org
To: Harold Huang <baymaxhuang@gmail.com>
Cc: netdev@vger.kernel.org, jasowang@redhat.com, pabeni@redhat.com,
davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3] tun: support NAPI for packets received from batched XDP buffs
Date: Wed, 02 Mar 2022 01:40:09 +0000 [thread overview]
Message-ID: <164618520995.21891.13359440725672676433.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220228033805.1579435-1-baymaxhuang@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Feb 2022 11:38:05 +0800 you wrote:
> In tun, NAPI is supported and we can also use NAPI in the path of
> batched XDP buffs to accelerate packet processing. What is more, after
> we use NAPI, GRO is also supported. The iperf shows that the throughput of
> single stream could be improved from 4.5Gbps to 9.2Gbps. Additionally, 9.2
> Gbps nearly reachs the line speed of the phy nic and there is still about
> 15% idle cpu core remaining on the vhost thread.
>
> [...]
Here is the summary with links:
- [net-next,v3] tun: support NAPI for packets received from batched XDP buffs
https://git.kernel.org/netdev/net-next/c/fb3f903769e8
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:[~2022-03-02 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:38 [PATCH] tun: support NAPI to accelerate packet processing Harold Huang
2022-02-24 17:22 ` Paolo Abeni
2022-02-25 3:36 ` Harold Huang
2022-02-25 3:46 ` Jason Wang
2022-02-25 9:02 ` [PATCH net-next v2] tun: support NAPI for packets received from batched XDP buffs Harold Huang
2022-02-28 2:15 ` Jason Wang
2022-02-28 4:06 ` Eric Dumazet
2022-02-28 4:20 ` Jason Wang
[not found] ` <CANn89iKLhhwGnmEyfZuEKjtt7OwTbVyDYcFUMDYoRpdXjbMwiA@mail.gmail.com>
2022-02-28 5:17 ` Jason Wang
2022-02-28 7:26 ` Harold Huang
2022-02-28 7:56 ` Jason Wang
2022-02-28 3:38 ` [PATCH net-next v3] " Harold Huang
2022-02-28 7:46 ` Jason Wang
2022-02-28 17:15 ` Stephen Hemminger
2022-03-01 1:47 ` Jason Wang
2022-03-01 1:58 ` Harold Huang
2022-03-02 1: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=164618520995.21891.13359440725672676433.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=baymaxhuang@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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