From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [RFC PATCH] tools:new tool for system info CPU, memory and huge pages Date: Mon, 16 May 2016 16:31:46 +0200 Message-ID: <3913390.TQD3aJPodK@xps13> References: <9407598A-CC69-4FEA-BB0F-F311E9B4126E@intel.com> <1769971.Of1QN7qGDT@xps13> <5CADB23E-9C5D-4FD0-BC19-1E9C79BF1033@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Wiles, Keith" Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 31D539AEE for ; Mon, 16 May 2016 16:31:48 +0200 (CEST) Received: by mail-wm0-f54.google.com with SMTP id g17so15562640wme.0 for ; Mon, 16 May 2016 07:31:48 -0700 (PDT) In-Reply-To: <5CADB23E-9C5D-4FD0-BC19-1E9C79BF1033@intel.com> 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" 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 not know or use or install these tools. I was hoping this one would be able to 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 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?