From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 00/11] Port XStats Date: Thu, 29 Oct 2015 14:10:54 +0100 Message-ID: <1535165.DJM3Z0EPLK@xps13> References: <1443606022-13581-2-git-send-email-harry.van.haaren@intel.com> <9689034CEF26614CAB4B447EEAAF98E918241CB2@wtl-exchp-1.sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Kyle Larose Return-path: Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by dpdk.org (Postfix) with ESMTP id 94CE48DA4 for ; Thu, 29 Oct 2015 14:12:05 +0100 (CET) Received: by wmff134 with SMTP id f134so24700897wmf.0 for ; Thu, 29 Oct 2015 06:12:05 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-10-29 08:55, Kyle Larose: > Ultimately the issue we are trying to solve is that there is no device > independent way to get any detailed statistics from NICs controlled by > DPDK. These statistics are quite useful, not just for diagnostics, but > for long term reporting. People using DPDK-based NFV products in a > production environment are not going to be happy that they cannot, for > example, see how the packet size bucket counters varied over time > using some sort of monitoring tool. I don't understand. The basic statistics are provided in a common API. The other ones are not available in every NICs and can only be interpreted while knowing the device. So what is the need exactly? Do you know an example of a networking layer having this kind of API?