From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by dpdk.org (Postfix) with ESMTP id 2025BCB92 for ; Thu, 16 Jun 2016 19:02:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1808; q=dns/txt; s=iport; t=1466096550; x=1467306150; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=OGMwTxz3bajpCiUDvhzV6EJlhqqScb6cCus3OLMXYlA=; b=iv6vpr6qwIXebfFu3DsDch5NIwZSMmTDoR7O/4ud5bTo++0nFdUlgMlC uzO1zD8aH1Vh45AKQO+88c67Awinz+OcvwHapQzCuES/IHLiWlMTz5x6+ skH5RHjzUVC8yBRcmHiVJx7HY8S6W/BjaDQutyXxeZmjOrneWRflE3sCf 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D9AQDi2mJX/5tdJa1egz6BUwa6VYF6h?= =?us-ascii?q?hcCgSw4FAEBAQEBAQFlJ4RLAQEBBDpLBAIBCBEEAQEfCQcyFAkIAQEEARIIiCj?= =?us-ascii?q?ASQEBAQEBAQEBAQEBAQEBAQEBAQEBARyGJ4RNihsBBIgTkF4BjiGPKY90AR42g?= =?us-ascii?q?3BuiEAHPn8BAQE?= X-IronPort-AV: E=Sophos;i="5.26,481,1459814400"; d="scan'208";a="286523846" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jun 2016 17:02:29 +0000 Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5GH2TmO031893 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 Jun 2016 17:02:29 GMT Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 16 Jun 2016 12:02:28 -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.1104.009; Thu, 16 Jun 2016 12:02:28 -0500 From: "John Daley (johndale)" To: Ruth Christen , "dev@dpdk.org" Thread-Topic: enic in passhtrough mode tx drops Thread-Index: AdHHzNjBZSTFZ75gSM2h3Xerbae5+gAA+3AQAAgAZ9A= Date: Thu, 16 Jun 2016 17:02:28 +0000 Message-ID: <187398f4c46f4ead9bf6b3df6e96f5af@XCH-RCD-007.cisco.com> References: <3C2AE3A004FB424A9D4DB093543E06A9E91B17C9@ILMB1.corp.radware.com> <3C2AE3A004FB424A9D4DB093543E06A9E91B18D0@ILMB1.corp.radware.com> In-Reply-To: <3C2AE3A004FB424A9D4DB093543E06A9E91B18D0@ILMB1.corp.radware.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.24.101.135] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] enic in passhtrough mode tx drops 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, 16 Jun 2016 17:02:30 -0000 Hi Ruth, I'm the enic pmd maintainer. To cut down on chatter I can work with you off= list and then we can post the result to dev@. I'd like to see the packet formed in the app and what's on the wire egress,= that you are sending on a configured VLAN, etc. I'll contact you directly. -john > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ruth Christen > Sent: Thursday, June 16, 2016 6:13 AM > To: dev@dpdk.org > Subject: [dpdk-dev] enic in passhtrough mode tx drops >=20 > Hi all, >=20 > I'm running a vm attached to 2 cisco Virtual Card Interfaces in passthrou= gh > mode in a cisco UCS. The vNICs are configured on access mode without VLAN > ID. >=20 > The incoming packets are arriving with 802.1q header containing vlan prio= rity > bit according to the class of service configured on the vNIC. I understoo= d this > is expected from a fiber channel Ethernet card. >=20 > 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. >=20 > If I run a simple l2fwd application where the same packet received in one > port is sent through the other the traffic works ok. >=20 > 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= ) >=20 >=20 >=20 > Is there a specific configuration to be added to the mbuff for the tx pac= kets > generated in the VM? Could be the vlan_tci/ ol_flags/ or any other missin= g > flag set? >=20 > Does somebody know the exact behavior of the enic card with the priority > tagging? >=20 >=20 >=20 > BTW in virtio mode the traffic works in both the flows. >=20 >=20 >=20 > Thanks a lot! >=20 >=20