From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by dpdk.org (Postfix) with ESMTP id C0B7F29D2 for ; Thu, 20 Oct 2016 20:49:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1493; q=dns/txt; s=iport; t=1476989361; x=1478198961; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=euZ2iBMhoFpr0O9xX44ccvONHGmhm1Pkhkp/ykrTqLU=; b=JEsRKCwGwDcOuTLu2TvUrcrmiK/48ocG9T3V5RgRyDkmv4+95b17MmLL eNFdHosHpsMMOELsK6XR8XOMeAmyNYvk3MyWGJXo/P7/N3s3rkcpp7KJp We015MnoWWkCcSkfHZW6y6BPkqzTBChxTI5sthjRodtNc5lxs/uph+b0V 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CNAQD3EAlY/4MNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgz4BAQEBAR2BVAeNLZZ8h16MX4IIHIYFAoF7PxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?iAQEBBAECNz8MBAIBCBEEAQEfBQQHIQcKFAkIAgQBDQUIiDADF79pDYNrAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHIY9hFWCR4dfBZlZNQGMAHiDDYF1hGmJJIhohBe?= =?us-ascii?q?DfwEeNliDPoE6cogZgQABAQE?= X-IronPort-AV: E=Sophos;i="5.31,372,1473120000"; d="scan'208";a="164981749" Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Oct 2016 18:49:20 +0000 Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u9KInK1c017081 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Oct 2016 18:49:20 GMT Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Oct 2016 13:49:19 -0500 Received: from xch-rcd-007.cisco.com ([173.37.102.17]) by XCH-RCD-007.cisco.com ([173.37.102.17]) with mapi id 15.00.1210.000; Thu, 20 Oct 2016 13:49:19 -0500 From: "John Daley (johndale)" To: Thomas F Herbert , "dev@dpdk.org" CC: Keith Burns , Edward Warnicke , "opnfv-tech-discuss@lists.opnfv.org" Thread-Topic: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up with OVS/DPDK with Cisco VIC adapter Thread-Index: AQHSKX8irf7DCRap6EiytgQ0AjsjYqCxsUbA Date: Thu, 20 Oct 2016 18:49:19 +0000 Message-ID: <495528db51e64f80a59348734a217a6c@XCH-RCD-007.cisco.com> References: <2986fc44-b2a1-f58c-62e0-eaf238a4fe08@redhat.com> In-Reply-To: <2986fc44-b2a1-f58c-62e0-eaf238a4fe08@redhat.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.19.145.149] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up with OVS/DPDK with Cisco VIC adapter X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 18:49:22 -0000 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 ; Edward Warnicke > ; opnfv-tech-discuss@lists.opnfv.org > Subject: [dpdk-dev] [opnfv-tech-discuss][apex][ovsnfv]Problem showed up > with OVS/DPDK with Cisco VIC adapter >=20 > All: >=20 > 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. >=20 In a UCS fabric, all frames between the VIC and the Fabric Interconnect wil= l be tagged. This is required to carry both VLAN information and, being a c= onverged adapter supporting both Ethernet and FCoE, traffic class. For non-= UCS fabric deployments, there is currently no way to turn off egress priori= ty tagging on the VIC adapter. If a packet being sent from DPDK to the enic= PMD is priority tagged (VLAN=3D0) 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 swit= ch that can't cope with priority tags. Is that the case here? > ... > -- > *Thomas F Herbert* > SDN Group > Office of Technology > *Red Hat*