From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 6D259FB85 for ; Tue, 20 Dec 2016 14:24:58 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 20 Dec 2016 05:24:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,378,1477983600"; d="scan'208,217";a="914391291" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.29]) ([10.237.220.29]) by orsmga003.jf.intel.com with ESMTP; 20 Dec 2016 05:24:36 -0800 To: dev@dpdk.org References: <20161216143919.4909-1-ferruh.yigit@intel.com> <20161216190257.6921-1-ferruh.yigit@intel.com> <20161216190257.6921-30-ferruh.yigit@intel.com> Cc: Jingjing Wu , Helin Zhang , Qi Zhang , Wenzhuo Lu , "Chen, Jing D" From: Ferruh Yigit Message-ID: <587a2f08-0541-3f99-d16f-1c14206f11e9@intel.com> Date: Tue, 20 Dec 2016 13:24:35 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161216190257.6921-30-ferruh.yigit@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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: Tue, 20 Dec 2016 13:24:58 -0000 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? >