From: Florian Westphal <fw@strlen.de>
To: wenxu <wenxu@ucloud.cn>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/3 nf-next] netfilter:nf_flow_table: Support bridge type flow offload
Date: Fri, 28 Jun 2019 08:06:17 +0200 [thread overview]
Message-ID: <20190628060617.az2quv4bodrenuli@breakpoint.cc> (raw)
In-Reply-To: <b2a48653-9f30-18a9-d0e1-eaa940a361a9@ucloud.cn>
wenxu <wenxu@ucloud.cn> wrote:
> ns21 iperf to 10.0.0.8 with dport 22 in ns22
> first time with OFFLOAD enable
>
> nft add flowtable bridge firewall fb2 { hook ingress priority 0 \; devices = { veth21, veth22 } \; }
> nft add chain bridge firewall ftb-all {type filter hook forward priority 0 \; policy accept \; }
> nft add rule bridge firewall ftb-all counter ct zone 2 ip protocol tcp flow offload @fb2
>
> # iperf -c 10.0.0.8 -p 22 -t 60 -i2
[..]
> [ 3] 0.0-60.0 sec 353 GBytes 50.5 Gbits/sec
>
> The second time on any offload:
> # iperf -c 10.0.0.8 -p 22 -t 60 -i2
> [ 3] 0.0-60.0 sec 271 GBytes 38.8 Gbits/sec
Wow, this is pretty impressive. Do you have numbers without
offload and no connection tracking?
Is this with CONFIG_RETPOLINE=y (just curious)?
next prev parent reply other threads:[~2019-06-28 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 10:32 [PATCH 1/3 nf-next] netfilter:nf_flow_table: Refactor flow_offload_tuple to support more offload method wenxu
2019-06-26 10:32 ` [PATCH 2/3 nf-next] netfilter:nf_flow_table: Support bridge type flow offload wenxu
2019-06-26 18:38 ` Florian Westphal
2019-06-26 19:19 ` Florian Westphal
2019-06-27 6:22 ` wenxu
2019-06-27 12:58 ` Pablo Neira Ayuso
2019-06-28 3:37 ` wenxu
2019-06-28 6:06 ` Florian Westphal [this message]
2019-06-28 9:51 ` wenxu
2019-06-26 18:40 ` Pablo Neira Ayuso
2019-06-26 10:32 ` [PATCH 3/3 nf-next] netfilter: Flow table support for the bridge family wenxu
2019-06-26 18:29 ` [PATCH 1/3 nf-next] netfilter:nf_flow_table: Refactor flow_offload_tuple to support more offload method Pablo Neira Ayuso
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=20190628060617.az2quv4bodrenuli@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wenxu@ucloud.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;
as well as URLs for NNTP newsgroup(s).