From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 2E07BADB5 for ; Tue, 24 Feb 2015 10:49:42 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 24 Feb 2015 01:49:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,637,1418112000"; d="scan'208";a="682521028" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by fmsmga002.fm.intel.com with ESMTP; 24 Feb 2015 01:49:39 -0800 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.103]) by IRSMSX151.ger.corp.intel.com ([169.254.4.7]) with mapi id 14.03.0195.001; Tue, 24 Feb 2015 09:49:38 +0000 From: "Jastrzebski, MichalX K" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v5 0/3] new headroom stats library and example application Thread-Index: AQHQTFE89sKNNirwW0yb77uFABjvv5z5r4bQgAR0TYCAAC5q0IAABCcAgAE+xlA= Date: Tue, 24 Feb 2015 09:49:38 +0000 Message-ID: <60ABE07DBB3A454EB7FAD707B4BB1582138EBD9C@IRSMSX109.ger.corp.intel.com> References: <1424191340-26451-1-git-send-email-pawelx.wodkowski@intel.com> <3091068.GKVt00SAyB@xps13> <60ABE07DBB3A454EB7FAD707B4BB1582138EB996@IRSMSX109.ger.corp.intel.com> <2047616.cJycthpmiM@xps13> In-Reply-To: <2047616.cJycthpmiM@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v5 0/3] new headroom stats library and example application 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: Tue, 24 Feb 2015 09:49:42 -0000 > > > I also feel that the name of this library is a bit too vague. Some pe= ople > > > were asking first what means "headroom". It's actually for CPU headro= om > > > monitoring. > > > What about "cpuheadroom", "cpuheadroomstat", "jobstat"? > > > > I think we can change the name to "cpuheadroom" as it describes more > clear this library. >=20 > If you're focusing on CPU usage with possible actions, yes. > If you're focusing on decision helper, jobstat would be better IMHO. We will change the name to "jobstats". Best regards Michal