DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Eelco Chaudron" <echaudro@redhat.com>
To: wenzhuo.lu@intel.com, konstantin.ananyev@intel.com
Cc: dev <dev@dpdk.org>
Subject: [dpdk-dev] VF of a X520 card does not process VLAN packets
Date: Tue, 18 Dec 2018 12:06:12 +0100	[thread overview]
Message-ID: <9D82C157-0E57-4A7D-B8F4-DEA4ED0EA1EC@redhat.com> (raw)

Hi,

I’m assigning a VF of an X520 card for DPDK/testpmd/OVS but it's not 
accepting tagged VLAN packets (it does accept tag 0).  Is this a known 
bug/limitation of the 82599ES chipset?

This is how I've tested it:

$ echo 1 > /sys/bus/pci/devices/0000\:05\:00.0/sriov_numvfs
$driverctl -v set-override 0000:05:10.0 vfio-pci
$./testpmd -c 7 -n 4 --socket-mem 2048,0 -w 0000:05:10.0 -- \
   --burst 64 -i --rxq=1 --txq=1 --rxd=4096 --txd=1024 \
   —coremask=6 --auto-start --port-topology=chained
EAL: Detected 28 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
...
testpmd>


I’m sending broadcast ARP packets:

Ethernet II, Src: 04:f4:bc:43:e1:00 (04:f4:bc:43:e1:00), Dst: 
ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
     Destination: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
         Address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
         .... ..1. .... .... .... .... = LG bit: Locally administered 
address (this is NOT the factory default)
         .... ...1 .... .... .... .... = IG bit: Group address 
(multicast/broadcast)
     Source: 04:f4:bc:43:e1:00 (04:f4:bc:43:e1:00)
         Address: 04:f4:bc:43:e1:00 (04:f4:bc:43:e1:00)
         .... ..0. .... .... .... .... = LG bit: Globally unique address 
(factory default)
         .... ...0 .... .... .... .... = IG bit: Individual address 
(unicast)
     Type: 802.1Q Virtual LAN (0x8100)
802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 10
     000. .... .... .... = Priority: Best Effort (default) (0)
     ...0 .... .... .... = CFI: Canonical (0)
     .... 0000 0000 1010 = ID: 10
     Type: ARP (0x0806)
     Padding: 2e2f303132333435363738393a3b
     Trailer: 3c3d3e3f404142434445464748494a4b4c4d4e4f50515253...
Address Resolution Protocol (request/gratuitous ARP)
     Hardware type: Ethernet (1)
     Protocol type: IP (0x0800)
     Hardware size: 6
     Protocol size: 4
     Opcode: request (1)
     [Is gratuitous: True]
     Sender MAC address: 00:00:00:00:00:00 (00:00:00:00:00:00)
     Sender IP address: 0.0.0.0 (0.0.0.0)
     Target MAC address: 00:00:00:00:00:00 (00:00:00:00:00:00)
     Target IP address: 0.0.0.0 (0.0.0.0)

No traffic is received, if you replace tag 10 with 0, packets are 
received.

Note that this is a simple reproducer with testpmd, but it's reported as 
part of an OVS integration. This works fine on the physical port, or 
with a VF on an XL710 card.

Any input appreciated.

Thanks,

Eelco

             reply	other threads:[~2018-12-18 11:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 11:06 Eelco Chaudron [this message]
2019-01-03 16:42 ` Eelco Chaudron
2019-01-18 11:25   ` Ananyev, Konstantin
2019-01-22 13:33     ` Eelco Chaudron
     [not found] <2601191342CEEE43887BDE71AB977258010D9070D3@irsmsx105.ger.corp.intel.com>
2019-01-23 14:09 ` Ananyev, Konstantin
2019-01-29  9:30   ` Zhao1, Wei

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=9D82C157-0E57-4A7D-B8F4-DEA4ED0EA1EC@redhat.com \
    --to=echaudro@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=wenzhuo.lu@intel.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).