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 AFF03A0A05; Wed, 20 Jan 2021 11:36:29 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 98078140EB9; Wed, 20 Jan 2021 11:36:29 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 9D323140E9D for ; Wed, 20 Jan 2021 11:36:27 +0100 (CET) IronPort-SDR: De6uqnq3OM9DnkyMmy6vhCJOY6Kon8S84gZOBb+Ke13W/U2hC6azlcrgAv0GQjXNkpPQt7YQRU 4jFrxBFSVhJw== X-IronPort-AV: E=McAfee;i="6000,8403,9869"; a="179168512" X-IronPort-AV: E=Sophos;i="5.79,360,1602572400"; d="scan'208";a="179168512" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jan 2021 02:36:26 -0800 IronPort-SDR: Xl/i1KiwGG8ReIUYn6NfE1ie1dYmcJLoy9nddb17EtbCDGSY0nLWkm5eMdQxIoeeM9G0X60peU 1J4nqA7PGEqA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,360,1602572400"; d="scan'208";a="354271100" Received: from fmsmsx606.amr.corp.intel.com ([10.18.126.86]) by orsmga006.jf.intel.com with ESMTP; 20 Jan 2021 02:36:26 -0800 Received: from shsmsx602.ccr.corp.intel.com (10.109.6.142) by fmsmsx606.amr.corp.intel.com (10.18.126.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 20 Jan 2021 02:36:25 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX602.ccr.corp.intel.com (10.109.6.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 20 Jan 2021 18:36:23 +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; Wed, 20 Jan 2021 18:36:23 +0800 From: "Zhang, Qi Z" To: Thomas Monjalon , "Guo, Jia" , "Yigit, Ferruh" , "Lu, Wenzhuo" , "Xing, Beilei" CC: "andrew.rybchenko@oktetlabs.ru" , "Iremonger, Bernard" , "Wu, Jingjing" , "Yang, Qiming" , "Wang, Haiyue" , "dev@dpdk.org" , "Su, Simei" , "orika@nvidia.com" , "getelson@nvidia.com" , "maxime.coquelin@redhat.com" , "jerinj@marvell.com" , "ajit.khaparde@broadcom.com" , "bingz@nvidia.com" , "Kinsella, Ray" , "dodji@redhat.com" , "david.marchand@redhat.com" Thread-Topic: [dpdk-dev v5] net/ice: enable eCPRI tunnel port configure in dcf Thread-Index: AQHW7htConIpECaPEk6wNgWQqJ8TgqowTWLw//970wCAAIbukP//fCcAgACHBtA= Date: Wed, 20 Jan 2021 10:36:23 +0000 Message-ID: References: <20201216085854.7842-1-jia.guo@intel.com> <13099790.6E2hLZTU9x@thomas> <55e2591279134fdf9c790a12f83b2b90@intel.com> <2370429.bghPMbm2R7@thomas> In-Reply-To: <2370429.bghPMbm2R7@thomas> 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] [dpdk-dev v5] net/ice: enable eCPRI tunnel port configure in dcf 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: Thomas Monjalon > Sent: Wednesday, January 20, 2021 6:31 PM > To: Guo, Jia ; Yigit, Ferruh ;= Lu, > Wenzhuo ; Xing, Beilei ; Zha= ng, > Qi Z > Cc: andrew.rybchenko@oktetlabs.ru; Iremonger, Bernard > ; Wu, Jingjing ; Yang= , > Qiming ; Wang, Haiyue ; > dev@dpdk.org; Su, Simei ; orika@nvidia.com; > getelson@nvidia.com; maxime.coquelin@redhat.com; jerinj@marvell.com; > ajit.khaparde@broadcom.com; bingz@nvidia.com; Kinsella, Ray > ; dodji@redhat.com; david.marchand@redhat.com > Subject: Re: [dpdk-dev v5] net/ice: enable eCPRI tunnel port configure in= dcf >=20 > 20/01/2021 11:23, Zhang, Qi Z: > > From: Thomas Monjalon > > > What is DCF? > > > > > > > > Its "Device Config Function" (DCF), please check ice.rst for detail. >=20 > Thank you. > As you know, I am interested in the privileged rights. > This is what I found in ice.rst: >=20 > A DCF PMD bounds to the device's trusted VF with ID 0 > [...] > #. Enable the VF0 trust on:: > ip link set dev enp24s0f0 vf 0 trust on >=20 > Does it mean only VF 0 can be trusted? Yes, currently we only allow VF0 have DCF capability, but that limitation m= ight be removed at some time. >=20