From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 54E579A91 for ; Mon, 16 May 2016 17:14:41 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 16 May 2016 08:14:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,627,1455004800"; d="scan'208";a="977963387" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga002.jf.intel.com with ESMTP; 16 May 2016 08:14:21 -0700 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX151.ger.corp.intel.com (163.33.192.59) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 16 May 2016 16:14:12 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.54]) by irsmsx112.ger.corp.intel.com ([169.254.1.10]) with mapi id 14.03.0248.002; Mon, 16 May 2016 16:14:12 +0100 From: "Richardson, Bruce" To: Thomas Monjalon , "Wiles, Keith" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC PATCH] tools:new tool for system info CPU, memory and huge pages Thread-Index: AQHRr3+6g536isBOw0ycBLAQHFWJGZ+7rB2g Date: Mon, 16 May 2016 15:14:12 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B035A5399D@IRSMSX103.ger.corp.intel.com> References: <9407598A-CC69-4FEA-BB0F-F311E9B4126E@intel.com> <1769971.Of1QN7qGDT@xps13> <5CADB23E-9C5D-4FD0-BC19-1E9C79BF1033@intel.com> <3913390.TQD3aJPodK@xps13> In-Reply-To: <3913390.TQD3aJPodK@xps13> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTc0Mzg0YjctYmIwNS00MTE3LWFjYmMtYWZiNWRlNzE1MzQwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Ilg1akw0VHVkc0NrOXVhYk15enQ4VDJ3QkUrQVBhS3IrcWJ5MGk2QzZBamM9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC PATCH] tools:new tool for system info CPU, memory and huge pages 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: Mon, 16 May 2016 15:14:41 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Monday, May 16, 2016 3:32 PM > To: Wiles, Keith > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC PATCH] tools:new tool for system info CPU, > memory and huge pages >=20 > 2016-05-16 14:11, Wiles, Keith: > > >2016-05-13 15:48, Wiles, Keith: > > >> I create this new tool to combine some information and use > /sys/devices instead. What I was hoping was some of you could try this > script and see if it works correctly. Also I was hope to find out if this > script is useful and what other features you would like in this type of > tool. > > > > > >What is the intent of this script? Is it to be used for bug report? > > >There already have some tools to display system informations. Why > > >adding one more? > > >Examples of useful tools: hwloc/lstopo, lspci, hugeadm. > > > > I was looking to replace the cpu_layout.py tool which uses the /procfs > instead of /sysfs, just figured we could then add some extra information > into this script as well. Yes, we have other tools, but some people do no= t > know or use or install these tools. I was hoping this one would be able t= o > display a number of things to help the developer and us in helping them > debug problems. > > > > Stephen Hemminger sent an email about the use of sysfs instead of > procfs. > > http://dpdk.org/ml/archives/dev/2016-May/038560.html >=20 > I agree that cpu_layout.py should be removed. > Should we implement something else? Or just point to existing tools? > Or call existing tools from a small script? > Is it the DPDK focus to develop and maintain such tool? +1 for pointing to existing tools. /Bruce