From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 9C82EFBF4 for ; Wed, 21 Dec 2016 01:56:06 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP; 20 Dec 2016 16:56:05 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,381,1477983600"; d="scan'208,217";a="1074622519" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga001.jf.intel.com with ESMTP; 20 Dec 2016 16:56:05 -0800 Received: from fmsmsx118.amr.corp.intel.com (10.18.116.18) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 20 Dec 2016 16:56:05 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx118.amr.corp.intel.com (10.18.116.18) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 20 Dec 2016 16:56:04 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX103.ccr.corp.intel.com ([10.239.4.69]) with mapi id 14.03.0248.002; Wed, 21 Dec 2016 08:56:03 +0800 From: "Lu, Wenzhuo" To: "Iremonger, Bernard" , "Yigit, Ferruh" , "dev@dpdk.org" CC: "Wu, Jingjing" , "Zhang, Helin" , "Zhang, Qi Z" , "Chen, Jing D" Thread-Topic: [dpdk-dev] [PATCH v5 29/29] net/i40e: set/clear VF stats from PF Thread-Index: AQHSWsRxG7cZm1HtHk6UjxIBBc0KJ6EQUXkAgAFCLiA= Date: Wed, 21 Dec 2016 00:56:02 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B54C602@shsmsx102.ccr.corp.intel.com> References: <20161216143919.4909-1-ferruh.yigit@intel.com> <20161216190257.6921-1-ferruh.yigit@intel.com> <20161216190257.6921-30-ferruh.yigit@intel.com> <587a2f08-0541-3f99-d16f-1c14206f11e9@intel.com> <8CEF83825BEC744B83065625E567D7C224D17A76@IRSMSX108.ger.corp.intel.com> In-Reply-To: <8CEF83825BEC744B83065625E567D7C224D17A76@IRSMSX108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v5 29/29] net/i40e: set/clear VF stats from PF X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2016 00:56:07 -0000 Hi all, > -----Original Message----- > From: Iremonger, Bernard > Sent: Tuesday, December 20, 2016 9:40 PM > To: Yigit, Ferruh; dev@dpdk.org > Cc: Wu, Jingjing; Zhang, Helin; Zhang, Qi Z; Lu, Wenzhuo; Chen, Jing D > Subject: RE: [dpdk-dev] [PATCH v5 29/29] net/i40e: set/clear VF stats fro= m PF >=20 > Hi Ferruh, >=20 > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferruh Yigit > > Sent: Tuesday, December 20, 2016 1:25 PM > > To: dev@dpdk.org > > Cc: Wu, Jingjing ; Zhang, Helin > > ; Zhang, Qi Z ; Lu, > > Wenzhuo ; Chen, Jing D > > Subject: Re: [dpdk-dev] [PATCH v5 29/29] net/i40e: set/clear VF stats > > from PF > > > > On 12/16/2016 7:02 PM, Ferruh Yigit wrote: > > > From: Qi Zhang > > > > > > This patch add support to get/clear VF statistics from PF side. > > > Two APIs are added: > > > rte_pmd_i40e_get_vf_stats. > > > rte_pmd_i40e_reset_vf_stats. > > > > > > Signed-off-by: Qi Zhang > > > --- > > > > <...> > > > > > diff --git a/drivers/net/i40e/rte_pmd_i40e_version.map > > > b/drivers/net/i40e/rte_pmd_i40e_version.map > > > index 8ac1bc8..7a5d211 100644 > > > --- a/drivers/net/i40e/rte_pmd_i40e_version.map > > > +++ b/drivers/net/i40e/rte_pmd_i40e_version.map > > > @@ -6,7 +6,9 @@ DPDK_2.0 { > > > DPDK_17.02 { > > > global: > > > > > > + rte_pmd_i40e_get_vf_stats; > > > rte_pmd_i40e_ping_vfs; > > > + rte_pmd_i40e_reset_vf_stats; > > > rte_pmd_i40e_set_tx_loopback; > > > rte_pmd_i40e_set_vf_broadcast; > > > rte_pmd_i40e_set_vf_mac_addr; > > > > Hi Wenzhuo, Mark, > > > > I think this is the list of all APIs added with this patchset. > > > > Just a question, what do you think following a logic in API naming as: > > __ ? > > > > So API names become: > > rte_pmd_i40e_tx_loopback_set; > > rte_pmd_i40e_vf_broadcast_set; > > rte_pmd_i40e_vf_mac_addr_set; > > rte_pmd_i40e_vfs_ping; > > rte_pmd_i40e_vf_stats_get; > > rte_pmd_i40e_vf_stats_reset; > > > > > > After above rename, rte_pmd_i40e_tx_loopback_set() is not giving a > > hint that this is something related to the PF controlling VF, perhaps > > we can rename the API ? > > > > Also rte_pmd_i40e_vfs_ping() can become rte_pmd_i40e_vf_ping_all() to > > be more consistent about _vf_ usage. > > > > Overall, they can be something like: > > rte_pmd_i40e_vf_broadcast_set; > > rte_pmd_i40e_vf_mac_addr_set; > > rte_pmd_i40e_vf_ping_all; > > rte_pmd_i40e_vf_stats_get; > > rte_pmd_i40e_vf_stats_reset; > > rte_pmd_i40e_vf_tx_loopback_set; > > > > What do you think? > > >=20 > I think the naming should be consistent with what has already been implem= ented > for the ixgbe PMD. > rte_pmd_ixgbe_set_all_queues_drop_en; > rte_pmd_ixgbe_set_tx_loopback; > rte_pmd_ixgbe_set_vf_mac_addr; > rte_pmd_ixgbe_set_vf_mac_anti_spoof; > rte_pmd_ixgbe_set_vf_split_drop_en; > rte_pmd_ixgbe_set_vf_vlan_anti_spoof; > rte_pmd_ixgbe_set_vf_vlan_insert; > rte_pmd_ixgbe_set_vf_vlan_stripq; >=20 > rte_pmd_ixgbe_set_vf_rate_limit; > rte_pmd_ixgbe_set_vf_rx; > rte_pmd_ixgbe_set_vf_rxmode; > rte_pmd_ixgbe_set_vf_tx; > rte_pmd_ixgbe_set_vf_vlan_filter; So, seems better to use the current names. Rework both ixgbe and i40e's lat= er. Not sure if it'll be counted as the ABI change if we change the ixgbe's= name. >=20 > Regards, >=20 > Bernard.