DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: dev@dpdk.org, stephen@networkplumber.org
Subject: Re: [dpdk-dev] [PATCH v2] usertools: show hugepages on POWER systems
Date: Fri, 05 Feb 2021 18:57:19 +0100	[thread overview]
Message-ID: <4648258.iI1bcg0Xb4@thomas> (raw)
In-Reply-To: <20201202205756.39577-1-drc@linux.vnet.ibm.com>

02/12/2020 21:57, David Christensen:
> The IBM PowerNV systems include NUMA nodes that don't have associated
> CPUs or hugepage memory.  Here is an example on an IBM AC922 system:
> 
> $ lscpu
> ...
> NUMA node0 CPU(s):   0-63
> NUMA node8 CPU(s):   64-127
> NUMA node252 CPU(s):
> ...
> 
> $ numastat -m
> ...
>                           Node 0          Node 8        Node 252
>                  --------------- --------------- ---------------
> MemTotal               126763.19       130785.06            0.00
> MemFree                119513.38       125294.44            0.00
> MemUsed                  7249.81         5490.62            0.00
> ...
> HugePages_Total             4.00         1734.00            0.00
> HugePages_Free              0.00            4.00            0.00
> HugePages_Surp              4.00         1730.00            0.00
> ...
> 
> Modify dpdk-hugepages.py to test for the ../hugepages directory before
> attempting to parse the hugepage entries.
> 
> Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>

Applied, thanks




      reply	other threads:[~2021-02-05 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 18:19 [dpdk-dev] [PATCH 1/1] " David Christensen
2020-12-02 18:32 ` Stephen Hemminger
2020-12-02 20:57 ` [dpdk-dev] [PATCH v2] " David Christensen
2021-02-05 17:57   ` Thomas Monjalon [this message]

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=4648258.iI1bcg0Xb4@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=stephen@networkplumber.org \
    /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).