From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from p01c11o149.mxlogic.net (p01c11o149.mxlogic.net [208.65.144.72]) by dpdk.org (Postfix) with ESMTP id 05F44803B for ; Fri, 10 Oct 2014 14:39:35 +0200 (CEST) Received: from unknown [66.151.187.11] (EHLO smtp.sonusnet.com) by p01c11o149.mxlogic.net(mxl_mta-8.1.0-0) over TLS secured channel with ESMTP id 545d7345.0.319503.00-208.867596.p01c11o149.mxlogic.net (envelope-from ); Fri, 10 Oct 2014 06:47:02 -0600 (MDT) X-MXL-Hash: 5437d5464fd0c9dd-a3f4feddf1c4d4490f3c6bfd0ab0c3e2ddc58635 Received: from INBA-HUB01.sonusnet.com (10.70.51.86) by psmwsonshc01.sonusnet.com (10.176.20.27) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Oct 2014 08:47:00 -0400 Received: from INBA-MAIL02.sonusnet.com ([10.70.51.89]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.03.0181.006; Fri, 10 Oct 2014 18:16:57 +0530 From: Karmarkar Suyash To: "dev@dpdk.org" Thread-Topic: Bug in outgoing packet with vmxnet3 with VLAN tagging Thread-Index: Ac/kh+KBhIm2UllpT42l44ZaAfJORQ== Date: Fri, 10 Oct 2014 12:46:57 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.70.54.108] MIME-Version: 1.0 X-AnalysisOut: [v=2.1 cv=fLkt3Pqe c=1 sm=1 tr=0 a=uJKQf5YWhIR+nybujYFUDg==] X-AnalysisOut: [:117 a=uJKQf5YWhIR+nybujYFUDg==:17 a=URNJFqk9g_oA:10 a=8Y7] X-AnalysisOut: [rnDDfXDYA:10 a=BLceEmwcHowA:10 a=xqWC_Br6kY4A:10 a=kUVcWBO] X-AnalysisOut: [SAAAA:8 a=YlVTAMxIAAAA:8 a=mMiTLaFNI-kEbCCb6ioA:9 a=2_m9wR] X-AnalysisOut: [EL7pRuLcC5:21 a=sPzlM7C8bNdicEI9:21 a=CjuIK1q_8ugA:10 a=yM] X-AnalysisOut: [hMjlubAAAA:8 a=SSmOFEACAAAA:8 a=l7PfmR7E0zVN_VCmJJIA:9 a=p] X-AnalysisOut: [bbra1DEYe0N_ISO:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=h] X-AnalysisOut: [TZeC7Yk6K0A:10 a=frz4AuCg-hUA:10] X-Spam: [F=0.5000000000; CM=0.500; MH=0.500(2014101008); S=0.200(2014051901)] X-MAIL-FROM: X-SOURCE-IP: [66.151.187.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Bug in outgoing packet with vmxnet3 with VLAN tagging 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: Fri, 10 Oct 2014 12:39:37 -0000 Hello All, When a outgoing packet is sent with data Len more than 1514 which will be a= case in VLAN (Max 1518 ) the packet is getting dropped because of the belo= w code snippet. This looks incorrect as in case of VLAN . FUNCTION NAME: vmxnet3_xmit_pkts /* Needs to minus ether header len */ if(txm->pkt.data_len > (hw-= >cur_mtu + ETHER_HDR_LEN)) { PMD_TX_LOG(= DEBUG, "Packet data_len higher than MTU\n"); rte_pktmbuf= _free(tx_pkts[nb_tx]); txq->stats.= drop_total++; nb_tx++; continue; } #define ETHER_ADDR_LEN 6 /**< Length of Ethernet address. */ #define ETHER_TYPE_LEN 2 /**< Length of Ethernet type field. */ #define ETHER_CRC_LEN 4 /**< Length of Ethernet CRC. */ #define ETHER_HDR_LEN \ (ETHER_ADDR_LEN * 2 + ETHER_TYPE_LEN) /**< Length of Ethernet h= eader. */ But in case of VLAN the Ethernet header is 18 bytes. Does this mean we do n= ot support VLAN for VMXNET3 PMD? Thanks. Regards Suyash Karmarkar