From: 万乐冰 <wanlebing@bytedance.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] ipv6 rte_flow supported on intel ixgbe/i40e dpdk 18.11.2
Date: Wed, 9 Dec 2020 04:00:37 -0800 [thread overview]
Message-ID: <CAKFdd2X30K3iYB=gswSFBGrqEm0qajdcB-wF6iCjN5+SR2QgeA@mail.gmail.com> (raw)
Hi Team:
recently I am using ipv6 rte_flow on intel ixgbe/i40e with dpdk
18.11.2,but it doesn't works.
i40e:
testpmd cmd:
./x86_64-native-linuxapp-gcc/app/testpmd -l 0,1-7,15,25-31 -n 4 -- -i
--pkt-filter-mode=perfect --rxq=8 --txq=8 --nb-cores=8 --pkt-filter-size=
*128K*
test flows:
- flow create 0 ingress pattern end actions rss types ipv6-other
ipv6-udp ipv6-tcp end queues 0 2 end / end
- flow create 0 ingress pattern eth / ipv6 dst is fdbd:dc01:11:152::74
/ end actions queue index 3 / end
- flow create 0 ingress pattern eth / ipv6 dst is fdbd:dc01:11:152::74
/ udp dst is 57993 / end actions queue index 4 / end
ixgbe:
testpmd cmd:
./x86_64-native-linuxapp-gcc/app/testpmd -l 0-10 -n 4 -- -i
--pkt-filter-mode=signature --rxq=8 --txq=8 --nb-cores=8
--pkt-filter-size=128K --pkt-filter-report-hash=match
test flows:
- flow create 0 ingress pattern end actions rss types ipv6-other
ipv6-udp ipv6-tcp end queues 0 2 end / end
- flow create 0 ingress pattern fuzzy thresh is 1 / ipv6 dst is
fcbd:dc01:1:222::abc8 / end actions queue index 3 / end
- flow create 0 ingress pattern fuzzy thresh spec 2 thresh last
0xfffffff0 thresh mask 0xffffffff / ipv6 dst is fcbd:dc01:1:222::abc8 /
udp dst is 58002 / end actions queue index 4 / end
all these flows can be created successful, but doesn't work, looking forward
some help.
next reply other threads:[~2020-12-10 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 12:00 万乐冰 [this message]
2020-12-10 17:39 ` Kevin Traynor
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='CAKFdd2X30K3iYB=gswSFBGrqEm0qajdcB-wF6iCjN5+SR2QgeA@mail.gmail.com' \
--to=wanlebing@bytedance.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).