DPDK usage discussions
 help / color / mirror / Atom feed
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK-20.11 and HUGEPAGES
Date: Wed, 26 May 2021 18:12:40 +0000	[thread overview]
Message-ID: <dcf5a411d1b446e99cf69f871f16a695@boeing.com> (raw)

Hi, I have a test environment based on RHEL VMs that are run from a hypervisor
that I have no administrative or physical access to. My only administrative control
is by ssh into the running VMs over the network where at least I have sudo access.

When I run my DPDK-20.11 application, it crashes because hugepages are not
configured. So, I allocated 2MB hugepages at runtime but the app still crashes
because there are no 1GB hugepages which on RHEL can only be set at boot time.

I found instructions for setting RHEL boot parameters that will allocate 1GB
hugepages at boot time, but I have not tried it because I am concerned that
if I mess something up and reboot the VM it may never come back.

So, I am wondering if DPDK-20.11 supports a "semi-huge" mode of operation
that allows it to run with only 2MB hugepages configured and no 1GB pages?
If so, what would be the way to set that up?

I have also tried invoking DPDK with "--no-huge". My application starts fine,
but at runtime it crashes out of a DPDK API call while processing an mbuf
for a received packet. I can give more details about this if there is a chance
it could be debugged - or, is "--no-huge" problematic in general?

Thanks - Fred


             reply	other threads:[~2021-05-26 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 18:12 Templin (US), Fred L [this message]
     [not found] <mailman.14682.1622060840.25471.users@dpdk.org>
2021-05-27  2:05 ` Huai-En Tseng
2021-05-27 11:49 Templin (US), Fred L

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=dcf5a411d1b446e99cf69f871f16a695@boeing.com \
    --to=fred.l.templin@boeing.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).