[v2,0/5] fix default max mtu size when device configured
Message ID | 20200922012338.11277-1-stevex.yang@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 94F47A04DE; Tue, 22 Sep 2020 03:42:56 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 434041D94C; Tue, 22 Sep 2020 03:42:55 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 11E761D8F1 for <dev@dpdk.org>; Tue, 22 Sep 2020 03:42:52 +0200 (CEST) IronPort-SDR: D3nel7AD5GdChQBlpt/10qDPOOe+XjeCYD6AqNg6xQWEODPx1rSRgTQW7iLUfnx8Fh8rSzD6Op 37wCJ39taNVQ== X-IronPort-AV: E=McAfee;i="6000,8403,9751"; a="148265185" X-IronPort-AV: E=Sophos;i="5.77,288,1596524400"; d="scan'208";a="148265185" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 18:42:47 -0700 IronPort-SDR: sIMNnT8b/iAD8qdC2Gf8795kfs9y64aQNxQ0qyEqNUqzZSEiVeP9KRDDpjdI9y+kfmSNvjJdR4 2egNvt76inog== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,288,1596524400"; d="scan'208";a="322045663" Received: from intel-npg-odc-srv01.cd.intel.com ([10.240.178.136]) by orsmga002.jf.intel.com with ESMTP; 21 Sep 2020 18:42:45 -0700 From: SteveX Yang <stevex.yang@intel.com> To: dev@dpdk.org Cc: wei.zhao1@intel.com, jia.guo@intel.com, qiming.yang@intel.com, qi.z.zhang@intel.com, jingjing.wu@intel.com, beilei.xing@intel.com, konstantin.ananyev@intel.com, SteveX Yang <stevex.yang@intel.com> Date: Tue, 22 Sep 2020 01:23:33 +0000 Message-Id: <20200922012338.11277-1-stevex.yang@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200916055212.25019-1-stevex.yang@intel.com> References: <20200916055212.25019-1-stevex.yang@intel.com> Subject: [dpdk-dev] [PATCH v2 0/5] fix default max mtu size when device configured X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Message
Steve Yang
Sept. 22, 2020, 1:23 a.m. UTC
testpmd will initialize default max packet length to 1518 which does't include vlan tag size in ether overheader. Once, send the max mtu length packet with vlan tag, the max packet length will exceed 1518 that will cause packets dropped directly from NIC hw side. configure the correct default max packet size in dev_config ops. v2: * change the max_rx_pkt_len via mtu_set ops; SteveX Yang (5): net/e1000: fix max mtu size packets with vlan tag cannot be received by default net/igc: fix max mtu size packets with vlan tag cannot be received by default net/ice: fix max mtu size packets with vlan tag cannot be received by default net/i40e: fix max mtu size packets with vlan tag cannot be received by default net/iavf: fix max mtu size packets with vlan tag cannot be received by default drivers/net/e1000/em_ethdev.c | 6 ++++++ drivers/net/i40e/i40e_ethdev.c | 5 +++++ drivers/net/i40e/i40e_ethdev_vf.c | 11 +++++++++++ drivers/net/iavf/iavf_ethdev.c | 5 +++++ drivers/net/ice/ice_ethdev.c | 5 +++++ drivers/net/igc/igc_ethdev.c | 7 ++++++- 6 files changed, 38 insertions(+), 1 deletion(-)