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 9F481A0C4B; Mon, 13 Sep 2021 04:46:25 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0E10F410DC; Mon, 13 Sep 2021 04:46:25 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mails.dpdk.org (Postfix) with ESMTP id 60B0B40041; Mon, 13 Sep 2021 04:46:23 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10105"; a="201726211" X-IronPort-AV: E=Sophos;i="5.85,288,1624345200"; d="scan'208";a="201726211" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Sep 2021 19:46:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.85,288,1624345200"; d="scan'208";a="698533930" Received: from fmsmsx604.amr.corp.intel.com ([10.18.126.84]) by fmsmga005.fm.intel.com with ESMTP; 12 Sep 2021 19:46:22 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by fmsmsx604.amr.corp.intel.com (10.18.126.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Sun, 12 Sep 2021 19:46:21 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX603.ccr.corp.intel.com (10.109.6.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Mon, 13 Sep 2021 10:46:20 +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.2242.012; Mon, 13 Sep 2021 10:46:20 +0800 From: "Zhang, Qi Z" To: "Yu, DapengX" , "Yang, Qiming" CC: "dev@dpdk.org" , "Wang, Haiyue" , "stable@dpdk.org" Thread-Topic: [PATCH v4] net/ice/base: get PF ID of VF's parent Thread-Index: AQHXqEiz5tXK7nGn10K1BnwT1pTvLauhQmgw Date: Mon, 13 Sep 2021 02:46:20 +0000 Message-ID: References: <20210831070333.549371-1-dapengx.yu@intel.com> <20210913024002.2868848-1-dapengx.yu@intel.com> In-Reply-To: <20210913024002.2868848-1-dapengx.yu@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 v4] net/ice/base: get PF ID of VF's parent 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: Yu, DapengX > Sent: Monday, September 13, 2021 10:40 AM > To: Yang, Qiming ; Zhang, Qi Z > > Cc: dev@dpdk.org; Wang, Haiyue ; Yu, DapengX > ; stable@dpdk.org > Subject: [PATCH v4] net/ice/base: get PF ID of VF's parent >=20 > From: Dapeng Yu >=20 > In original implementation, if DCF is created on PF1, the PF ID is still = 0, but not > 1. Without the right PF ID, the ACL will not work. >=20 > This patch makes VF to get its parent's physical function ID. >=20 > Fixes: 0b02c9519432 ("net/ice: handle PF initialization by DCF") > CC: stable@dpdk.org >=20 > Signed-off-by: Dapeng Yu > Acked-by: Haiyue Wang Applied to dpdk-next-net-intel. Thanks Qi