From: Paolo Abeni <pabeni@redhat.com>
To: Harold Huang <baymaxhuang@gmail.com>, netdev@vger.kernel.org
Cc: jasowang@redhat.com, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tun: support NAPI to accelerate packet processing
Date: Thu, 24 Feb 2022 18:22:04 +0100 [thread overview]
Message-ID: <1de9e991f6c109d5986c857bc176e03d5e167944.camel@redhat.com> (raw)
In-Reply-To: <20220224103852.311369-1-baymaxhuang@gmail.com>
Hello,
On Thu, 2022-02-24 at 18:38 +0800, Harold Huang 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 NPAI, GRO is also supported. The iperf shows that the throughput
Very minor nit: typo above NPAI -> NAPI
> could be improved from 4.5Gbsp to 9.2Gbps per stream.
>
> Reported-at: https://lore.kernel.org/netdev/CAHJXk3Y9_Fh04sakMMbcAkef7kOTEc-kf84Ne3DtWD7EAp13cg@mail.gmail.com/T/#t
> Signed-off-by: Harold Huang <baymaxhuang@gmail.com>
Additionally, please specify explicitly the target tree into the patch
subject.
Cheers,
Paolo
next prev parent reply other threads:[~2022-02-24 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:38 Harold Huang
2022-02-24 17:22 ` Paolo Abeni [this message]
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
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=1de9e991f6c109d5986c857bc176e03d5e167944.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=baymaxhuang@gmail.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®