From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 6FBB511D9 for ; Tue, 31 Jan 2017 14:13:14 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP; 31 Jan 2017 05:13:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,315,1477983600"; d="scan'208";a="59509047" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga005.fm.intel.com with ESMTP; 31 Jan 2017 05:13:12 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.77]) by IRSMSX104.ger.corp.intel.com ([163.33.3.159]) with mapi id 14.03.0248.002; Tue, 31 Jan 2017 13:13:12 +0000 From: "Mcnamara, John" To: Thomas Monjalon , "Horton, Remy" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v9 1/7] lib: add information metrics library Thread-Index: AQHScZx9YpxXbnjMPkK4u7T5/8AqXaFRPfCAgAEvZuA= Date: Tue, 31 Jan 2017 13:13:11 +0000 Message-ID: References: <1484751943-22877-1-git-send-email-remy.horton@intel.com> <1484751943-22877-2-git-send-email-remy.horton@intel.com> <1659974.13GHXkxjEr@xps13> In-Reply-To: <1659974.13GHXkxjEr@xps13> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzA5YmY2MTMtNjEyMi00ZTBhLTgyMTEtZjljODMzNzJjZGNiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImxlR3J4ZnJwdHdhZFphS1JpZ2grdjlnSGQwVktLMXgxeXRzUmRoeDVMY0k9In0= x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v9 1/7] lib: add information metrics library X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 13:13:14 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Monday, January 30, 2017 3:50 PM > To: Horton, Remy > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v9 1/7] lib: add information metrics > library >=20 > Hi Remy, >=20 > > This patch adds a new information metric library that allows other > > modules to register named metrics and update their values. It is > > intended to be independent of ethdev, rather than mixing ethdev and > > non-ethdev information in xstats. >=20 > I'm still not convinced by this library, and this introduction does not > help a lot. >=20 > I would like to thanks Harry for the review of this series. > If we had more opinions or enthousiasm about this patch, it would be > easier to accept this new library and assert it is the way to go. Hi, The RFCs for this library (initially two, merged into one) have been up sin= ce October, during the 16.11 timeframe. Comments were made and applied. http://dpdk.org/ml/archives/dev/2016-October/049571.html http://dpdk.org/ml/archives/dev/2016-October/048390.html I'm concerned that these new comments/reservations are coming in very, very= late in the 17.02 release cycle. If there hasn't been a lot of opinions or enthusiasm then equally there has= n't been other reservations. If there had been we would have addressed them= . > It could be a matter of technical board discussion if we had a clear > explanation of the needs, the pros and cons of this design. We are happy to have the design discussed at the Technical Board. We would = also like the inclusion of this library in RC3 to be discussed since that i= s still our desired outcome.=20 We have, as any other company would have, customers awaiting features, deve= lopers committed to timelines, and testing and integration roadmaps. Blocki= ng or delaying features at the last moment isn't an effective model that we= , and I'm sure other companies, can work with. As such, it is probably best, that all current and future RFCs are reviewed= at the Technical Board and that the board gives an indication on whether t= he proposal is acceptable for upstreaming or not.=20 > The overview for using this library should be given in the prog guide. We will add a section to the Programmers Guide. John