From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind_com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=9YQUs50HRC3sVFQHV3XD9SStRpuWEKIKHHDhhUgep0g=; b=sySqq83Vn3OhWFk4obWJrDd08PjyRubi8TqsLavvWinw/mtWa51oWIkPpUt1fmMShj YVz7Ejbe2vmO7MeXGYZ1ogxlQl1DCih2hXk38Yl04A1/hiAwtc8D8ZSfjQiEiiaT5brF OGtVLux5BoSwItbVDOZoe/sTqF5P9vKUIsE6+hE9V6/AidWfYi+5Vqc6q7iT1YtCyKh4 d19qoQB51fHV+waaRZsfZSkMKazOosU3qyqVrquGeCmVqZBGWAD79Be7+voZnHtwT8Zl 8nK2+IaI6czBfoPrf3VJVRRGVfy3iEc6CJkG+apaoGm8E5QEtUoq+83BU9JdOJfxsm3g jh1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=9YQUs50HRC3sVFQHV3XD9SStRpuWEKIKHHDhhUgep0g=; b=hJhBIDWaTg2dD6fIyucRNHz5AAj3pKOgllVFSOEj+syQzAAvbHJE3CN9kpTaJjLrbx x6tlt5otMz8LarPxywBaIKwswudolW2Goew+obRKZlu/l5u4SMiVUuk4wNltRkf4CzuI IoyL8JbFZtBz08YasEkyvIaip1ZK6FTWzlmxiclwQFiycXdekT9XX0l32NJS5JaDJy3Z skRjQP2Kj5DTs0tn0BPxTzPFf1+/xJBJw5KP9nkZ9wj8RUAOn3cSTTzELZEGGgHD5yQB x2OxgX8rgjOGuoUUJygARYH3Z7+qOPdPNKcMG24jHkUvpHubbet99BV1B8dA3xuAwNSQ F3eg== X-Gm-Message-State: ALoCoQlb30Dy1tYKH0IEYnxjBCG7+lcaC/PZSiFBOi5grADysfmv6+H3VFAy7IsK3o7fWv4p8l2h X-Received: by 10.28.88.135 with SMTP id m129mr3929562wmb.67.1446124325420; Thu, 29 Oct 2015 06:12:05 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id t20sm9141224wme.0.2015.10.29.06.12.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Oct 2015 06:12:04 -0700 (PDT) From: Thomas Monjalon To: Kyle Larose Date: Thu, 29 Oct 2015 14:10:54 +0100 Message-ID: <1535165.DJM3Z0EPLK@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1443606022-13581-2-git-send-email-harry.van.haaren@intel.com> <9689034CEF26614CAB4B447EEAAF98E918241CB2@wtl-exchp-1.sandvine.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 00/11] Port XStats 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: Thu, 29 Oct 2015 13:12:05 -0000 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?