From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: hugepages on both sockets
Date: Fri, 4 Apr 2025 22:24:19 +0000 [thread overview]
Message-ID: <CH3PR01MB8470E9DD7027F53B1B58E3E58FA92@CH3PR01MB8470.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
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, ',');
In eal_common_string_fns.c gdb failed at the line shown below.
rte_strsplit(char *string, int stringlen,
char **tokens, int maxtokens, char delim)
{
int i, tok = 0;
int tokstart = 1; /* first token is right at start of string */
if (string == NULL || tokens == NULL)
goto einval_error;
for (i = 0; i < stringlen; i++) {
if (string[i] == '\0' || tok >= maxtokens)
break;
if (tokstart) {
tokstart = 0;
tokens[tok++] = &string[i];
}
if (string[i] == delim) {
string[i] = '\0'; <<<< Fails here with segmentation fault.
tokstart = 1;
}
}
return tok;
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.
Any help is appreciated.
Thanks,
Ed
[-- Attachment #2: Type: text/html, Size: 6264 bytes --]
next reply other threads:[~2025-04-04 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 22:24 Lombardo, Ed [this message]
2025-04-04 22:39 ` Dmitry Kozlyuk
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=CH3PR01MB8470E9DD7027F53B1B58E3E58FA92@CH3PR01MB8470.prod.exchangelabs.com \
--to=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).