DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andriy Berestovskyy <Andriy.Berestovskyy@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] usertools: use /sys/devices/system/cpu for CPU layout script
Date: Tue, 25 Apr 2017 12:19:47 +0200	[thread overview]
Message-ID: <a98eb80c-ff04-224d-a8c7-41323c44035c@caviumnetworks.com> (raw)
In-Reply-To: <1810447.5BRUVpxoUJ@xps>

Hi,

On 25.04.2017 10:48, Thomas Monjalon wrote:
> Do you think it is really a good idea to keep and maintain this script
> in DPDK? It was intentionnally not exported in "make install".
> I think it is a bit out of scope, and I wonder which alternatives
> do we have? I know hwloc/lstopo, but there are probably others.

hwloc does not work on my target, but you are right, there are a variety 
of tools for that. For example, I prefer numactl (option -H) because it 
also allows to do many useful things, like bind CPUs to one node and 
memory allocations to another.

At the moment the script is just like the lscpu, which is preinstalled 
on Ubuntu and mentioned in the documentation alongside with the cpu_layout.

We could try to make the script more useful, for example, show which NIC 
is on which NUMA node. Still, it will be just a subset of functionality 
of tools like hwloc...


Regards,
Andriy

  reply	other threads:[~2017-04-25 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 12:21 Andriy Berestovskyy
2017-04-25  8:48 ` Thomas Monjalon
2017-04-25 10:19   ` Andriy Berestovskyy [this message]
2017-04-25 11:01     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a98eb80c-ff04-224d-a8c7-41323c44035c@caviumnetworks.com \
    --to=andriy.berestovskyy@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).