DPDK patches and discussions
 help / color / mirror / Atom feed
From: =?gb18030?B?dGIuYmluZ2Vs?= <tb.bingel@qq.com>
To: =?gb18030?B?dXNlcnM=?= <users@dpdk.org>,
	=?gb18030?B?ZGV2?= <dev@dpdk.org>
Subject: [dpdk-dev] dpdk-i40e could not receive vlan packet whose ip_len was bigger than 1496
Date: Tue, 9 Jul 2019 15:21:33 +0800	[thread overview]
Message-ID: <tencent_4AC22F08E1BA8414E3E7BF55746492024E08@qq.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 3023 bytes --]

Hi all,


I found dpdk-i40e could not receive vlan packet whose ip_len was bigger than 1496, 


and I tested the same test cases with i350(igb)  network card, NO such issue.


Was it a bug in DPDK? Thanks!


Test Environment£º
* netcard : Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP
* CPU : Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz
* OS : Ubuntu 16.04 
* DPDK£º 19.05


How to reproduce£¿
------------------------------------------------------------------------
Step 1:  start kni example
$ sudo ./build/kni -l 0-5 -n 4 -- -P -p 0x1 -m --config="(0,1,3)" 
EAL: Detected 48 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: PCI device 0000:19:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:3b:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:3b:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
APP: Initialising port 0 ...
 
Checking link status
..done
Port0 Link Up - speed 40000Mbps - full-duplex
APP: ========================
APP: KNI Running
APP: kill -SIGUSR1 90114
APP:     Show KNI Statistics.
APP: kill -SIGUSR2 90114
APP:     Zero KNI Statistics.
APP: ========================
APP: Lcore 1 is reading from port 0
APP: Lcore 2 has nothing to do
APP: Lcore 3 is writing to port 0
APP: Lcore 4 has nothing to do
APP: Lcore 0 has nothing to do
APP: Lcore 5 has nothing to do
APP: Configure network interface of 0 up
APP: vEth0 NIC Link is Up 40000 Mbps (AutoNeg) Full Duplex.



Step 2: configure KNI interface WITHOUT VLAN
$ sudo ifconfig vEth0 192.168.99.141/24


Step 3: configure KNI interface WITH VLAN ID

$ sudo vconfig add vEth0 589
Added VLAN with VID == 589 to IF -:vEth0:-
$ sudo ifconfig vEth0 192.168.100.141/24
 

Step 4£ºping KNI IP(no VLAN) from antoher PC
$ ping -c 1 -s 1472 -M do 192.168.99.141     
PING 192.168.99.141 (192.168.99.141) 1472(1500) bytes of data.  <<<< It's OK for ip payload 1500
1480 bytes from 192.168.99.141: icmp_seq=1 ttl=64 time=7.53 ms


Step 5: ping KNI VLAN IP from anther PC
$ ping -c 1 -s 1468 -M do 192.168.100.141  
PING 192.168.100.141 (192.168.100.141) 1468(1496) bytes of data.   <<<< It's OK for ip payload 1496
1476 bytes from 192.168.100.141: icmp_seq=1 ttl=64 time=4.66 ms



$ ping -c 1 -s 1469 -M do 192.168.100.141  
PING 192.168.100.141 (192.168.100.141) 1469(1497) bytes of data.   <<< failed for ip payload 1497
^C
--- 192.168.100.141 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


------------------------------------------------------------------------

                 reply	other threads:[~2019-07-09  7:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=tencent_4AC22F08E1BA8414E3E7BF55746492024E08@qq.com \
    --to=tb.bingel@qq.com \
    --cc=dev@dpdk.org \
    --cc=users@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).