DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruth Christen <RuthC@Radware.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] enic in passhtrough mode tx drops
Date: Thu, 16 Jun 2016 13:13:02 +0000	[thread overview]
Message-ID: <3C2AE3A004FB424A9D4DB093543E06A9E91B18D0@ILMB1.corp.radware.com> (raw)
In-Reply-To: <3C2AE3A004FB424A9D4DB093543E06A9E91B17C9@ILMB1.corp.radware.com>

Hi all,

I'm running a vm attached to 2 cisco Virtual Card Interfaces in passthrough mode in a cisco UCS. The vNICs are configured on access mode without VLAN ID.

The incoming packets are arriving with 802.1q header containing vlan priority bit according to the class of service configured on the vNIC. I understood this is expected from a fiber channel Ethernet card.

According to dpdk documentation there's a need to set the VLAN_STRIP_OFFLOAD flag and call rte_eth_dev_set_vlan_offload on the ports.

If I run a simple l2fwd application where the same packet received in one port is sent through the other the traffic works ok.

If I generate the packets in my vm and send them out traffic doesn't work. (I tried send the traffic out with/without a 802.1q header with priority bit)



Is there a specific configuration to be added to the mbuff for the tx packets generated in the VM? Could be the vlan_tci/ ol_flags/ or any other missing flag set?

Does somebody know the exact behavior of the enic card with the priority tagging?



BTW in virtio mode the traffic works in both the flows.



Thanks a lot!

       reply	other threads:[~2016-06-16 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C2AE3A004FB424A9D4DB093543E06A9E91B17C9@ILMB1.corp.radware.com>
2016-06-16 13:13 ` Ruth Christen [this message]
2016-06-16 17:02   ` John Daley (johndale)
2016-06-21  7:34   ` Ruth Christen

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=3C2AE3A004FB424A9D4DB093543E06A9E91B18D0@ILMB1.corp.radware.com \
    --to=ruthc@radware.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).