From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Horton Subject: Re: xstats performance Date: Fri, 8 Jul 2016 12:15:34 +0100 Message-ID: References: <5773EB79.1090509@6wind.com> <8870166.MVVViF2IlQ@xps13> <99e03d76-b896-2146-274c-2f3d83eee899@intel.com> <2488e9da-d0a2-598f-25e3-e68293c082fe@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" , Olivier MATZ To: Rasesh Mody , Thomas Monjalon Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id D024258D9 for ; Fri, 8 Jul 2016 13:15:36 +0200 (CEST) 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" On 07/07/2016 23:59, Rasesh Mody wrote: [..] > We have submitted the QEDE and BNX2X PMD xstats patches with recent > API changes. Seen & Acked. > During the xstats change verification, it was observed that the order > in which xstats names are fetched don't seem to match the order in > which xstats values are fetched. When populating the xstats names, we > order them as driver specific xstats names and then standard stats > names. Whereas, while populating the xstats values, we populate the > standard stats values and then the driver specific xstats values. Had a look. Patch on the way.. ..Remy