DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas F Herbert <therbert@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Keith Burns <alagalah@gmail.com>,
	Edward Warnicke <hagbard@gmail.com>,
	"opnfv-tech-discuss@lists.opnfv.org"
	<opnfv-tech-discuss@lists.opnfv.org>
Subject: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up with OVS/DPDK with Cisco VIC adapter
Date: Tue, 18 Oct 2016 16:35:04 -0400	[thread overview]
Message-ID: <2986fc44-b2a1-f58c-62e0-eaf238a4fe08@redhat.com> (raw)

All:

This is not necessarily related to VPP but rather to OVS/DPDK.

In OPNFV we found the following problem when using UCS NIC.

The UCS fabric seems to set a VLAN tag on untagged packets.

Any thoughts from DPDK and VPP folks would be appreciated.

http://dpdk.org/doc/guides-16.07/nics/enic.html

https://jira.opnfv.org/browse/APEX-333

It is currently deploying DPDK 16.04 and OVS 2.5.90

I could not find a user accessible setting to do this that would work. 
The workaround for now we came up with is to set a flow in OVS to strip 
the tag.

https://gerrit.opnfv.org/gerrit/#/c/23315/

Another solution is to set the nic to strip the vlan in rte eth code or 
write a DPDK "app" to set the nic.

http://dpdk.org/doc/guides-16.07/nics/enic.html

--TFH


-- 
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*

             reply	other threads:[~2016-10-18 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 20:35 Thomas F Herbert [this message]
2016-10-19 14:27 ` [dpdk-dev] [opnfv-tech-discuss] [apex][ovsnfv][fuel]Problem " Tim Rozet
2016-10-19 15:11   ` Michal Skalski
2016-10-19 17:00     ` Tim Rozet
2016-10-20 18:49 ` [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem " John Daley (johndale)

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=2986fc44-b2a1-f58c-62e0-eaf238a4fe08@redhat.com \
    --to=therbert@redhat.com \
    --cc=alagalah@gmail.com \
    --cc=dev@dpdk.org \
    --cc=hagbard@gmail.com \
    --cc=opnfv-tech-discuss@lists.opnfv.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).