From: "John Daley (johndale)" <johndale@cisco.com>
To: Thomas F Herbert <therbert@redhat.com>, "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: Re: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up with OVS/DPDK with Cisco VIC adapter
Date: Thu, 20 Oct 2016 18:49:19 +0000 [thread overview]
Message-ID: <495528db51e64f80a59348734a217a6c@XCH-RCD-007.cisco.com> (raw)
In-Reply-To: <2986fc44-b2a1-f58c-62e0-eaf238a4fe08@redhat.com>
Hi,
Please see inline.
Thanks,
john
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas F Herbert
> Sent: Tuesday, October 18, 2016 1:35 PM
> To: dev@dpdk.org
> Cc: Keith Burns <alagalah@gmail.com>; Edward Warnicke
> <hagbard@gmail.com>; opnfv-tech-discuss@lists.opnfv.org
> Subject: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up
> with OVS/DPDK with Cisco VIC adapter
>
> 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.
>
In a UCS fabric, all frames between the VIC and the Fabric Interconnect will be tagged. This is required to carry both VLAN information and, being a converged adapter supporting both Ethernet and FCoE, traffic class. For non-UCS fabric deployments, there is currently no way to turn off egress priority tagging on the VIC adapter. If a packet being sent from DPDK to the enic PMD is priority tagged (VLAN=0) or has no VLAN tag, the default VLAN tag (as set up in CIMC/UCSM manager) will be inserted. This should only be an issue with C-series UCS servers connected point to point or through a switch that can't cope with priority tags. Is that the case here?
> ...
> --
> *Thomas F Herbert*
> SDN Group
> Office of Technology
> *Red Hat*
prev parent reply other threads:[~2016-10-20 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:35 Thomas F Herbert
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 ` John Daley (johndale) [this message]
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=495528db51e64f80a59348734a217a6c@XCH-RCD-007.cisco.com \
--to=johndale@cisco.com \
--cc=alagalah@gmail.com \
--cc=dev@dpdk.org \
--cc=hagbard@gmail.com \
--cc=opnfv-tech-discuss@lists.opnfv.org \
--cc=therbert@redhat.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).