From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by dpdk.org (Postfix) with ESMTP id A9B0B8DAF for ; Wed, 20 Jan 2016 18:18:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=740; q=dns/txt; s=iport; t=1453310328; x=1454519928; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=Ngb/NUl1A04fktvpc9A3OZR99T6IjJJL7aBO3ykPrFg=; b=Q4AVyL5LvVANj//hyLemhX/ZhmxVqAm+dNDJWYeCFxXxUpe6j3ncaZhW J1/uZslx4HLveq9vyfOjmwCzOD1jK11gKImCbHgzqGP7dOMQusRXWOgoZ mUCMcwjnCz0S2OusTyNescRK+uF9VLyFCslZVQfXEbY8g51jvgcunP8fP A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AjAgAfwZ9W/4MNJK1egzqBRYhRsmsBD?= =?us-ascii?q?YFkh1c4FAEBAQEBAQF/C4Q7OlEBPkImAQQbiBOhA58VAQEIAQEBARyGOo4ABZc?= =?us-ascii?q?EAY1XjwdEjXwBHgEBQoNnhwB8AQEB?= X-IronPort-AV: E=Sophos;i="5.22,321,1449532800"; d="scan'208";a="228786001" Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jan 2016 17:18:32 +0000 Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u0KHIWjP023332 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 20 Jan 2016 17:18:32 GMT Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 20 Jan 2016 11:18:32 -0600 Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1104.009; Wed, 20 Jan 2016 11:18:32 -0600 From: "David Harton (dharton)" To: "dev@dpdk.org" Thread-Topic: Future Direction for rte_eth_stats_get() Thread-Index: AdFToifrMKxGpVsMS/qKv8msWpPa2wABEBgw Date: Wed, 20 Jan 2016 17:18:31 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.250.67] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [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: Wed, 20 Jan 2016 17:18:49 -0000 I see that some of the rte_eth_stats have been marked deprecated in 2.2 tha= t are returned by rte_eth_stats_get(). Applications that utilize any numbe= r of device types rely on functions like this one to debug I/O issues. Is there a reason the stats have been deprecated? Why not keep the stats i= n line with the standard linux practices such as rtnl_link_stats64? Note, using rte_eth_xstats_get() does not help for this particular scenario= because a common binary API is needed to communicate through various layer= s and also provide a consistent view/meaning to users. The xstats is excel= lent for debugging device specific scenarios but can't help in scenarios wh= ere a static view is expected. Thanks, Dave