DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: hugepages on both sockets
Date: Sun, 6 Apr 2025 08:38:07 -0700	[thread overview]
Message-ID: <20250406083807.761af093@hermes.local> (raw)
In-Reply-To: <CH3PR01MB8470D34EDA4FC3D38A1FF9C58FAB2@CH3PR01MB8470.prod.exchangelabs.com>

On Sun, 6 Apr 2025 00:56:45 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:

> Hi Dmitry,
> You pointed out a good point.  I passed the literal "--socket-mem=2048,2048" in the array provided to rte_eal_init() function, where DPDK EAL tries to tokenize in place the string and it crashes trying to modify a readonly memory.  I don't know why DPDK does this.  But now I know, and I now see four rtemap_x files created for two sockets.

The function rte_eal_init() expects arguments to be like the arguments passed to main().
Those arguments are not read-only. You need to use strdup (or strdupa) to make mutable versions.

      reply	other threads:[~2025-04-06 15:38 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
2025-04-06  0:56   ` Lombardo, Ed
2025-04-06 15:38     ` Stephen Hemminger [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=20250406083807.761af093@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=Ed.Lombardo@netscout.com \
    --cc=dmitry.kozliuk@gmail.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).