From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D3B4FA0A03; Tue, 19 Jan 2021 07:30:13 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4D6DB140D36; Tue, 19 Jan 2021 07:30:13 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 5791F140D35; Tue, 19 Jan 2021 07:30:12 +0100 (CET) IronPort-SDR: yrw5Tm8m3L25KihK+hgyIDp8U6WMMlltLVVUWCCup9KG4rZIrMv/3hjkyNKtfiOYVkZzbfqMX5 qzrRICbzpZRg== X-IronPort-AV: E=McAfee;i="6000,8403,9868"; a="158064577" X-IronPort-AV: E=Sophos;i="5.79,358,1602572400"; d="scan'208";a="158064577" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jan 2021 22:30:02 -0800 IronPort-SDR: s1NdBB2Poj/pupDM3f4MGRLquRHPwTw2pxdJDtQkTqjD2fhBlJb5HKGIhtvA7lQr6iZgEXwF6y cu9IyIJllyfQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,358,1602572400"; d="scan'208";a="573466822" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by fmsmga005.fm.intel.com with ESMTP; 18 Jan 2021 22:30:02 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by fmsmsx602.amr.corp.intel.com (10.18.126.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 18 Jan 2021 22:30:02 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX601.ccr.corp.intel.com (10.109.6.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 19 Jan 2021 14:30:00 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.1713.004; Tue, 19 Jan 2021 14:30:00 +0800 From: "Zhang, Qi Z" To: "Zhang, AlvinX" CC: "dev@dpdk.org" , "Zhang, AlvinX" , "stable@dpdk.org" Thread-Topic: [PATCH v7] net/ixgbe: fix configuration of max frame size Thread-Index: AQHW7iOTnrWlEhr2E0+STGDlzU6a66oufJ3A Date: Tue, 19 Jan 2021 06:30:00 +0000 Message-ID: <4f1a612fd68e4e63ac561e29db9a0ed2@intel.com> References: <20210118083507.13544-1-alvinx.zhang@intel.com> <20210119052551.21204-1-alvinx.zhang@intel.com> In-Reply-To: <20210119052551.21204-1-alvinx.zhang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v7] net/ixgbe: fix configuration of max frame size X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Zhang,Alvin > Sent: Tuesday, January 19, 2021 1:26 PM > To: Zhang, Qi Z > Cc: dev@dpdk.org; Zhang, AlvinX ; stable@dpdk.org > Subject: [PATCH v7] net/ixgbe: fix configuration of max frame size >=20 > From: Alvin Zhang >=20 > For some types of NIC, jumbo frame is not supported in IOV mode, so if a = VF > requests to configure the frame size to not bigger than IXGBE_ETH_MAX_LEN= , > the kernel driver returns 0, but the DPDK ixgbe PMD returens -1, this wil= l cause > the VF to fail to start when the PF driven by DPDK ixgbe PMD. >=20 > This patch keeps ixgbe PMD's handling mode consistent with kernel driver = in > above situation. >=20 > In addition, the value set by the command IXGBE_VF_SET_LPE represents the > max frame size, not the mtu. >=20 > Fixes: 1b9ea09c067b ("ixgbe: support X550") > Fixes: 95a27b3ba5f5 ("net/ixgbe: enable jumbo frame for VF") > Cc: stable@dpdk.org >=20 > Signed-off-by: Alvin Zhang Applied to dpdk-next-net-intel. Thanks Qi