> -----Original Message----- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Monday, May 16, 2016 3:32 PM > To: Wiles, Keith <keith.wiles at intel.com> > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [RFC PATCH] tools:new tool for system info CPU, > memory and huge pages > > 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?
+1 for pointing to existing tools. /Bruce
