From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id B705311F5 for ; Thu, 29 Oct 2015 15:02:32 +0100 (CET) Received: by wmff134 with SMTP id f134so24928043wmf.1 for ; Thu, 29 Oct 2015 07:02:32 -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=MRG65YJ/ZeHdZgMTnC4N56NerdX5TKraz1XfDigwKLM=; b=axKf9tRS/cQ0eEOSrNrMtLCnzlLf46BavLtfZIF2zgg4IWzZwpbsEeXyMVtuvjQxTy Th79MIBRVXKdJTQabi+0VVEGVlOfb2WDFdPg1yYqALtn5jhoxGy3h3163Nfkz8OlBeiQ uK+egsD2Wov/Sicj3pTRkBamG1Q73VbUlq+Y0NTbahLmn9ZZgdFRP6rRonsiuSTG7Kxl +Yr8ycwbgBvLXEBR5M+Pj2AWtMvTp5Pf1s/g+QeDoOLW3ft28fWFQwrNM+FvF4oi7TRO oySVgM+gEVyrHrs2XpjES3/br2HNykA4G19t699zPtZhH0o15CLPDKR6Dv4f7m3fNjYf fv1w== 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=MRG65YJ/ZeHdZgMTnC4N56NerdX5TKraz1XfDigwKLM=; b=Dov8UsLHWjN6dqBOB/t/rxzaPiHWU2rs1kvUJEZWVLL6lK4FKcx7b6ITbaRaeERNKG OMKbnqPotBFsOd0mAkcbo59zKf55FfolqYy9EZPO1BmZv8aAbMfBKuwhGa/7cLIeOEJN TesSCs1ifGoScd2CmDqgorc3rOyEBlL7OYp4KcztSdrm30+j98VHJh3f1pbbKplqKSA0 AQtn/+N/q2mVBaEVViY/w/k46mbEpkXpfCH18HMru5qSmZ2aZL9nGBhBCzgx4dPYAyb8 gjik49I1WhhMhpfyWLCfHyaPyTqf/gS5CKbfPLrzDMLDypEIVQk+R0+Itn7C4VDz63kd V7KQ== X-Gm-Message-State: ALoCoQl+C7zOUr73LEsbLLGa8QeBsU2o4yc2BJKRGNUaurkmKPItlArwl+owwJ5Dy9GtI4HvlSpS X-Received: by 10.28.144.143 with SMTP id s137mr7485104wmd.26.1446127352375; Thu, 29 Oct 2015 07:02:32 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id c67sm9358363wmh.11.2015.10.29.07.02.31 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Oct 2015 07:02:31 -0700 (PDT) From: Thomas Monjalon To: Kyle Larose Date: Thu, 29 Oct 2015 15:01:21 +0100 Message-ID: <14919853.N7JUKnnn3e@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> <1535165.DJM3Z0EPLK@xps13> 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 14:02:32 -0000 2015-10-29 09:57, Kyle Larose: > On Thu, Oct 29, 2015 at 9:10 AM, Thomas Monjalon > wrote: > > > 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? > > The need is to provide information to users about what sort of traffic > is being seen by the device, and why the hardware is behaving the way > it is, leveraging as much as possible the capabilities of the hardware > with minimal effort (i.e. not implementing an abstraction layer at a > higher level). > > These are quite useful for diagnosing wider network issues > (configuration, misbehaving devices, dirty fibers/etc). The common API > doesn't expose the more detailed information requested by the various > ethernet mibs. Of course, not all stats are applicable to all devices > (e.g. collisions), but those that are available are still invaluable. Thanks for the explanation. > > Do you know an example of a networking layer having this kind of API? > > I have worked with SDKs for a few different physical switches and > NPUs. They all provide this sort of API. I think it is quite common > with networking equipment such as routers or switches. These stats > tend to be exposed over SNMP at the very least, and often within local > utilities on the devices themselves. So what is missing currently? Just having a consistent naming of similar counters?