xl710 gtp ddp profile

[Ivan_Dyukov]

I'm investigating a packet classification possibilities of the xl710. I have downloaded gtp ddp profile to nic and try to filter gtpu and ipv6 etc traffic to different queues. I have used these guides:

https://software.intel.com/content/www/us/en/develop/articles/dynamic-device-personalization-for-intel-ethernet-700-series.html 

https://doc.dpdk.org/dts/test_plans/queue_region_test_plan.html

https://doc.dpdk.org/dts/test_plans/ddp_gtp_qregion_test_plan.html

 It works ok, for simple gtp packets. like:
========================
Frame 277: 178 bytes on wire (1424 bits), 178 bytes captured (1424 bits)
Ethernet II, Src: IntelCor_a6:21:24 (3c:fd:fe:a6:21:24), Dst: HandHeld_30:40:50 (00:10:20:30:40:50)
Internet Protocol Version 4, Src: 1.1.1.1, Dst: 2.2.2.2
User Datagram Protocol, Src Port: 45050, Dst Port: 2152
GPRS Tunneling Protocol
Flags: 0x32
001. .... = Version: GTP release 99 version (1)
...1 .... = Protocol type: GTP (1)
.... 0... = Reserved: 0
.... .0.. = Is Next Extension Header present?: No
.... ..1. = Is Sequence Number present?: Yes
.... ...0 = Is N-PDU number present?: No
Message Type: T-PDU (0xff)
Length: 140
TEID: 0x6be3b2be (1810084542)
Sequence number: 0x0001 (1)
Internet Protocol Version 4, Src: 3.3.3.146, Dst: 4.4.4.108
User Datagram Protocol, Src Port: 53244, Dst Port: 57069
ADwin configuration protocol
=====================================

in case of extension header of gtp. the ddp profile does not work at all. example of header:
Frame 1: 190 bytes on wire (1520 bits), 190 bytes captured (1520 bits)
Ethernet II, Src: fa:16:3e:c6:08:4c (fa:16:3e:c6:08:4c), Dst: IETF-VRRP-VRID_01 (00:00:5e:00:01:01)
802.1Q Virtual LAN, PRI: 0, DEI: 0, ID: 2220
Internet Protocol Version 4, Src: 172.22.99.51, Dst: 172.20.21.55
User Datagram Protocol, Src Port: 2152, Dst Port: 2152
GPRS Tunneling Protocol
Flags: 0x36
001. .... = Version: GTP release 99 version (1)
...1 .... = Protocol type: GTP (1)
.... 0... = Reserved: 0
.... .1.. = Is Next Extension Header present?: Yes <---------- THIS FIELD!!!!!!!
.... ..1. = Is Sequence Number present?: Yes
.... ...0 = Is N-PDU number present?: No
Message Type: T-PDU (0xff)
Length: 136
TEID: 0x00000c66 (3174)
Sequence number: 0xba79 (47737)
Next extension header type: Unknown (0x85) <---------- THIS FIELD!!!!!!!
Extension header
Extension Header Length: 1
Next extension header type: No more extension headers (0x00)
T-PDU Data: 4500008016d600003d113c71ac14155b7a13eea317ed1405...
Internet Protocol Version 4, Src: 172.20.21.91, Dst: 122.19.238.163
User Datagram Protocol, Src Port: 6125, Dst Port: 5125
Data (100 bytes)
=============================

Could you please confirm that extension header of GTP is not supported yet. Do you have any plans to support it?

there are steps which I used in testpmd:

build/app/testpmd -l 9,10,11,12 -n 4 --socket-mem=4096,4096 -w 0000:0b:00.1 -- -i --rxq=16 --txq=16 --forward-mode=rxonly
port stop 0
ddp add 0 /root/gtp.pkgo,/root/gtp.bak
port start 0

port config 0 pctype mapping update 25 25
port config 0 pctype 25 hash_inset clear all
port config 0 pctype 25 hash_inset set field 50
port config 0 pctype 25 hash_inset set field 51
port config 0 pctype 25 hash_inset set field 52
port config 0 pctype 25 hash_inset set field 53
port config 0 pctype 25 hash_inset set field 54
port config 0 pctype 25 hash_inset set field 55
port config 0 pctype 25 hash_inset set field 56
port config 0 pctype 25 hash_inset set field 57
port config all rss 25

port config 0 pctype mapping update 22 26
port config 0 pctype 22 hash_inset clear all
port config 0 pctype 22 hash_inset set field 44
port config 0 pctype 22 hash_inset set field 45
port config all rss 26

port config 0 pctype mapping update 23 23
port config 0 pctype 23 hash_inset clear all
port config 0 pctype 23 hash_inset set field 44
port config 0 pctype 23 hash_inset set field 45
port config all rss 23

port config all rss all
set fwd rxonly
set verbose 8
start

set port 0 queue-region region_id 0 queue_start_index 4 queue_num 1
set port 0 queue-region region_id 1 queue_start_index 5 queue_num 1
set port 0 queue-region region_id 2 queue_start_index 6 queue_num 1
set port 0 queue-region region_id 3 queue_start_index 7 queue_num 1
set port 0 queue-region region_id 4 queue_start_index 8 queue_num 1
set port 0 queue-region region_id 5 queue_start_index 9 queue_num 1
set port 0 queue-region region_id 7 queue_start_index 11 queue_num 1

set port 0 queue-region region_id 0 flowtype 41
set port 0 queue-region region_id 1 flowtype 31
set port 0 queue-region region_id 2 flowtype 43
set port 0 queue-region region_id 3 flowtype 33
set port 0 queue-region region_id 4 flowtype 26
set port 0 queue-region region_id 5 flowtype 23
set port 0 queue-region region_id 7 flowtype 25

set port 0 queue-region flush on

example of packet is attached
Thanks,
Ivan

[AlfredoS_Intel]

Hi Ivan_dyukov,

Thank you for posting in our Intel® Ethernet Communities Page.

You have a very interesting project here.

Based on the resources that you are using, are you using an Intel Data Plan Development Kit?

We look forward to hearing from you. If we do not get your reply, we will follow up after 3 business days.

Best Regards,

Alfred S

Intel® Customer Support

[Ivan_Dyukov]

Hello Alfred S,

I'm using http://fast.dpdk.org/rel/dpdk-20.08.tar.xz library.

Actually my question is not related to dpdk. I've asked about Intel DDP profile. Could you please confirm that extension header of GTP is not supported yet. Do you have any plans to support it?

Best regards,

Ivan

[Brian_J_Intel1 · Accepted solution]

#IAMINTEL

Ivan,

I am Solutions Architect in the Ethernet Products Group at Intel and want to point you to our DDP GTP-EXT Package that might address your needs.

The new GTP-EXT Package has not been posted as a stand-alone package yet but is available in the 25_2.zip Complete Driver Pack in the DDP - 710_Series folder you will find the zip for it. 

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

 Hopefully this helps address your needs.

Brian 

[Jiang]

Is there any difference between pctype 16(17) and 18(19) ? Did you make a mistake? 

Two of them should be UL, right?

Table 4.

Packet Classifier Types and Input Set

PCTYPE	PCTYPE Description	Hash Input Set	FD Input Set
12	IPv4 PFCP Session	IP4-S, IP4-D
13	IPv4 PFCP Node	IP4-S, IP4-D
14	IPv6 PFCP Session	IP6-S, IP6-D
15	IPv6 PFCP Node	IP6-S, IP6-D
16	GTP-U, PDU Type DL, IPv4 PDU	IP4-S, GTP TEID	GTP TEID
17	GTP-U, PDU Type DL, IPv6 PDU	IP6-S, GTP TEID	GTP TEID
18	GTP-U, PDU Type DL, IPv4 PDU	IP4-D, GTP TEID	GTP TEID
19	GTP-U, PDU Type DL, IPv6 PDU	IP6-D, GTP TEID	GTP TEID
22	GTP-U, IPv4 PDU	IP4-S, IP4-D, GTP TEID	GTP TEID
23	GTP-U, IPv6 PDU	IP6-S, IP6-D, GTP TEID	GTP TEID
24	GTP-U, non PDU	GTP TEID	GTP TEID
25	GTP-C, IPv4	GTP TEID	GTP TEID
38	GTP-C, IPv6	GTP TEID	GTP TEID

[AlfredoS_Intel]

Hi Ivan_dyukov,

Thank you providing those information.

Please allow us some time to check on this. 

We will get back to you no later than 3 business days from now.

Best Regards,

Alfred S

Intel® Customer Support 

[AlfredoS_Intel]

Hi Ivan_dyukov,

We would like to check if the suggestions of our esteemed community member addressed your concern.

We look forward to hearing from you. Should we not hear from you, we will follow up after 3 business days.

Best Regards,

Alfred S

Intel® Customer Support 

[Ivan_Dyukov]

Thanks for great support. It has solved the issue.

Best regards,

Ivan