From: Jiri Benc <jbenc@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Paolo Abeni <pabeni@redhat.com>,
Or Gerlitz <gerlitz.or@gmail.com>,
Simon Horman <simon.horman@netronome.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Linux Netdev List <netdev@vger.kernel.org>,
oss-drivers@netronome.com,
John Hurley <john.hurley@netronome.com>,
Paul Blakey <paulb@mellanox.com>, Jiri Pirko <jiri@mellanox.com>,
Roi Dayan <roid@mellanox.com>
Subject: Re: tc H/W offload issue with vxlan tunnels [was: nfp: flower vxlan tunnel offload]
Date: Wed, 27 Sep 2017 17:27:29 +0200 [thread overview]
Message-ID: <20170927172729.5b7a8c44@griffin> (raw)
In-Reply-To: <20170927125509.GG1944@nanopsycho.orion>
On Wed, 27 Sep 2017 14:55:09 +0200, Jiri Pirko wrote:
> So where do you attach the tc filter instead of eth0? vxlan0?
Yes, vxlan0. I'm pasting the example from earlier in this thread again:
This will match:
ip link add vxlan0 type vxlan dstport 4789 dev eth0 external
ip link set dev vxlan0 up
tc qdisc add dev vxlan0 ingress
ethtool -K eth0 hw-tc-offload on
tc filter add dev vxlan0 protocol ip parent ffff: flower enc_key_id 102 \
enc_dst_port 4789 src_ip 3.4.5.6 skip_sw action [...]
while this must NOT match:
ip link add vxlan0 type vxlan dstport 4789 dev eth0 external
ip link set dev vxlan0 up
tc qdisc add dev eth0 ingress
ethtool -K eth0 hw-tc-offload on
tc filter add dev eth0 protocol ip parent ffff: flower enc_key_id 102 \
enc_dst_port 4789 src_ip 3.4.5.6 skip_sw action [...]
Jiri
next prev parent reply other threads:[~2017-09-27 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 8:29 tc H/W offload issue with vxlan tunnels [was: nfp: flower vxlan tunnel offload] Paolo Abeni
2017-09-27 9:17 ` Jiri Pirko
2017-09-27 9:46 ` Paolo Abeni
2017-09-27 11:11 ` Jiri Pirko
2017-09-27 12:31 ` Paolo Abeni
2017-09-27 12:55 ` Jiri Pirko
2017-09-27 15:27 ` Jiri Benc [this message]
2017-09-27 15:35 ` Jiri Pirko
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=20170927172729.5b7a8c44@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=john.hurley@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=pabeni@redhat.com \
--cc=paulb@mellanox.com \
--cc=roid@mellanox.com \
--cc=simon.horman@netronome.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;
as well as URLs for NNTP newsgroup(s).