From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1044] [dpdk-22.07] ice_iavf_fdir: the ipv4/6 gtpu_eh rule not take effect
Date: Thu, 30 Jun 2022 08:34:36 +0000 [thread overview]
Message-ID: <bug-1044-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1044
Bug ID: 1044
Summary: [dpdk-22.07] ice_iavf_fdir: the ipv4/6 gtpu_eh rule
not take effect
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: zhiminx.huang@intel.com
Target Milestone: ---
DPDK version:
22.07-rc2:7cac53f205ebd04d8ebd3ee6a9dd84f698d4ada3
OS:
4.18.0-348.el8.x86_64/redhat8.5
Compiler:
gcc version 8.5.0 20210514 (Red Hat 8.5.0-4)
Hardware platform:
Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware:
Intel Corporation Ethernet Controller E810-C for QSFP [8086:1592]
NIC firmware:
driver: 1.9.3_dirty
firmware-version: 4.00 0x80011845 1.3236.0
ddp: ICE COMMS Package version 1.3.37.0
Reproduced Step:
1.
echo 1 > /sys/bus/pci/devices/0000\:ca\:00.0/sriov_numvfs
2.
./usertools/dpdk-devbind.py -b vfio-pci 0000:ca:01.0
3.
ip link set ens25f0 vf 0 mac 00:11:22:33:44:55
4.
./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 4 -- -i --rxq=16
--txq=16
5.
set fwd rxonly
set verbose 1
start
flow create 0 ingress pattern eth / ipv4 / udp / gtpu teid is 0x12345678 /
gtp_psc qfi is 0x34 / end actions queue index 1 / end
6.
Ether(src="a4:bf:01:51:27:ca", dst="00:11:22:33:44:55")/IP(src="192.168.0.20",
dst="192.168.0.21")/UDP(dport=2152)/GTP_U_Header(gtp_type=255,teid=0x12345678)/GTPPDUSessionContainer(type=1,P=1,QFI=0x34)/IP()/Raw("x"*20)
output:
testpmd> port 0/queue 10: received 1 packets
src=A4:BF:01:51:27:CA - dst=00:11:22:33:44:55 - type=0x0800 - length=102 -
nb_segs=1 - RSS hash=0x43723baa - RSS queue=0xa - hw ptype: L2_ETHER
L3_IPV4_EXT_UNKNOWN TUNNEL_GTPU INNER_L3_IPV4_EXT_UNKNOWN INNER_L4_NONFRAG -
sw ptype: L2_ETHER L3_IPV4 L4_UDP - l2_len=14 - l3_len=20 - l4_len=8 - VXLAN
packet: packet type =32913, Destination UDP port =2152, VNI = 1193046,
last_rsvd = 120 - Receive queue=0xa
ol_flags: RTE_MBUF_F_RX_RSS_HASH RTE_MBUF_F_RX_L4_CKSUM_GOOD
RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
expect output:
testpmd> port 0/queue 1: received 1 packets
src=A4:BF:01:51:27:CA - dst=00:11:22:33:44:55 - type=0x0800 - length=102 -
nb_segs=1 - RSS hash=0x9ce7492b - RSS queue=0x1 - hw ptype: L2_ETHER
L3_IPV4_EXT_UNKNOWN TUNNEL_GTPU INNER_L3_IPV4_EXT_UNKNOWN INNER_L4_NONFRAG -
sw ptype: L2_ETHER L3_IPV4 L4_UDP - l2_len=14 - l3_len=20 - l4_len=8 - VXLAN
packet: packet type =32913, Destination UDP port =2152, VNI = 1193046,
last_rsvd = 120 - Receive queue=0x1
ol_flags: RTE_MBUF_F_RX_RSS_HASH RTE_MBUF_F_RX_L4_CKSUM_GOOD
RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
Regression
Is this issue a regression: (Y/N) Y
commit 0718b7716c9516fca458695f7a0195b1f45d4778 (HEAD, refs/bisect/bad)
Author: Gregory Etelson <getelson@nvidia.com>
Date: Thu Jun 16 21:01:03 2022 +0300
net: fix GTP PSC headers
Fix bitmap fields order in little endian section of GTP PSC headers.
Fixes: e8ca1479cdc4 ("net: add extension header for GTP PSC")
Cc: stable@dpdk.org
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Reviewed-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Aman Singh <aman.deep.singh@intel.com>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-06-30 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:34 bugzilla [this message]
2022-07-27 7:42 ` [Bug 1044] [dpdk-22.07] ice_iavf_fdir: the ipv4/6 gtpu_eh rule not take effect bugzilla
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=bug-1044-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.