DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: users <users@dpdk.org>
Subject: Re: hugepage mapping to memseg failure
Date: Wed, 11 Sep 2024 01:36:44 +0300	[thread overview]
Message-ID: <20240911013644.58eaf50e@sovereign> (raw)
In-Reply-To: <CH3PR01MB84701012A4FCD4E6D03CD2628F9A2@CH3PR01MB8470.prod.exchangelabs.com>

2024-09-10 20:42 (UTC+0000), Lombardo, Ed:
> Hi Dmitry,
> If I use grub for hugepages will the hugepages always be contiguous and we won’t see the mapping to memsegs issue?

There are no guarantees about physical addresses.
On bare metal, getting continuous addresses at system startup is more likely.
On VM, I think, it is always less likely because host memory is fragmented.

> I am investigating your option 2 you provided to see how much VIRT memory increases.

There might be a third option.
If your HW and hypervisor permit accessing IOMMU from guests
and if the NIC can be bound to vfio-pci driver,
then you could use IOVA-as-VA (--iova-mode=va)
and have no issues with physical addresses ever.

Out of curiosity, why legacy memory mode is preferable for your app?

  reply	other threads:[~2024-09-10 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 22:23 hugepage allocation mapping failure Lombardo, Ed
2024-09-06 13:42 ` hugepage mapping to memseg failure Lombardo, Ed
2024-09-07 20:35   ` Dmitry Kozlyuk
2024-09-10 20:42     ` Lombardo, Ed
2024-09-10 22:36       ` Dmitry Kozlyuk [this message]
2024-09-11  4:26         ` Lombardo, Ed

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=20240911013644.58eaf50e@sovereign \
    --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).