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 0ABF0918F for ; Fri, 22 Jan 2016 12:07:55 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 22 Jan 2016 03:07:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,330,1449561600"; d="scan'208";a="896010873" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga002.jf.intel.com with ESMTP; 22 Jan 2016 03:07:54 -0800 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 22 Jan 2016 11:07:53 +0000 Received: from irsmsx106.ger.corp.intel.com ([169.254.8.197]) by irsmsx111.ger.corp.intel.com ([169.254.2.198]) with mapi id 14.03.0248.002; Fri, 22 Jan 2016 11:07:53 +0000 From: "Tahhan, Maryam" To: "David Harton (dharton)" , "dev@dpdk.org" Thread-Topic: Future Direction for rte_eth_stats_get() Thread-Index: AdFToifrMKxGpVsMS/qKv8msWpPa2wABEBgwAFcuL6A= Date: Fri, 22 Jan 2016 11:07:52 +0000 Message-ID: <1A27633A6DA49C4A92FCD5D4312DBF536B09F44B@IRSMSX106.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWY2MTI4MmEtYTRlNi00MWM0LWI3MjUtZmVhYjBjZTI5NjU2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiWHFqWlRNa1Z4d0xsOHRRWGpmYlp3citFZlFlaTh2ZjNkNlJkeFhBVEN5Zz0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Future Direction for rte_eth_stats_get() X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 11:07:56 -0000 Hi David Some of the stats were HW specific rather than generic stats that should be= exposed through rte_eth_stats and were migrated to the xstats API. http://= dpdk.org/ml/archives/dev/2015-June/019915.html. The naming was also not gen= eric enough to cover some of the drivers and in some cases what was exposed= was only a partial view of the relevant stats. They were marked as deprecated to deter people from using them in the futur= e, but haven't been removed from all the driver implementations yet. The Re= gisters that remain undeprecated are those considered to be generic. Which registers are you particularly interested in that have been deprecate= d? Can you elaborate on what you mean by " scenarios where a static view is= expected " Thanks in advance. Best Regards,=20 Maryam > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Harton > (dharton) > Sent: Wednesday, January 20, 2016 5:19 PM > To: dev@dpdk.org > Subject: [dpdk-dev] Future Direction for rte_eth_stats_get() >=20 > I see that some of the rte_eth_stats have been marked deprecated in 2.2 > that are returned by rte_eth_stats_get(). Applications that utilize any > number of device types rely on functions like this one to debug I/O > issues. >=20 > Is there a reason the stats have been deprecated? Why not keep the > stats in line with the standard linux practices such as rtnl_link_stats64= ? >=20 > Note, using rte_eth_xstats_get() does not help for this particular scenar= io > because a common binary API is needed to communicate through > various layers and also provide a consistent view/meaning to users. The > xstats is excellent for debugging device specific scenarios but can't hel= p > in scenarios where a static view is expected. >=20 > Thanks, > Dave