DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: hugepages on both sockets
Date: Sat, 5 Apr 2025 01:39:47 +0300	[thread overview]
Message-ID: <e66932f6-5c01-4b62-91fa-41f0b9b2bd1d@gmail.com> (raw)
In-Reply-To: <CH3PR01MB8470E9DD7027F53B1B58E3E58FA92@CH3PR01MB8470.prod.exchangelabs.com>

Hi Ed,

On 05.04.2025 01:24, Lombardo, Ed wrote:
>
> Hi,
>
> I tried to pass into dpdk_eal_init() the argument 
> --socket-mem=2048,2048” and I get segmentation error when strsplit() 
> function is called
>
>         arg_num = rte_strsplit(strval, len,
>
>                         arg, RTE_MAX_NUMA_NODES, ',');
>
Please forgive me for the stupid question:
"strval" points to a mutable buffer, like "char strval[] = "2048,2048", 
not "char *strval = "2048,2048"?

> If I pass “--socket_mem=2048”, --socket-mem=2048”, rte_eal_init() does 
> not complain.
>
> Not sure if this would ensure both CPU sockets will host 2-1G 
> hugepages?  I suspect it doesn’t because I only see to rtemap_0 and 
> rtemap_1 in /mnt/huge directory.  I think I should see four total.
>
> # /opt/dpdk/dpdk-hugepages.py -s
>
> Node Pages Size Total
>
> 0    2     1Gb    2Gb
>
> 1    2     1Gb    2Gb
>
> I don’t know if I should believe the above output showing 2Gb on Numa 
> Nodes 0 and 1.
>
You are correct, --socket-mem=2048 allocates 2048 MB total, spreading 
between nodes.

  reply	other threads:[~2025-04-04 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 22:24 Lombardo, Ed
2025-04-04 22:39 ` Dmitry Kozlyuk [this message]
2025-04-06  0:56   ` Lombardo, Ed
2025-04-06 15:38     ` Stephen Hemminger

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=e66932f6-5c01-4b62-91fa-41f0b9b2bd1d@gmail.com \
    --to=dmitry.kozliuk@gmail.com \
    --cc=Ed.Lombardo@netscout.com \
    --cc=users@dpdk.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).