DPDK patches and discussions
 help / color / mirror / Atom feed
From: Baruch Even <baruch@weka.io>
To: stephen@networkplumber.org
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: Hugepage migration
Date: Tue, 30 May 2023 16:51:34 +0300	[thread overview]
Message-ID: <CAKye4QY0p-sni0X0Ly6WS=qtwqZ=twj7X_Rvu5U2e8WMsmzeZw@mail.gmail.com> (raw)
In-Reply-To: <20230529183514.1febf224@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]

I have tested the MAP_LOCKED, it doesn't help in this case. I do intend to
report to the kernel but was wondering if others have hit upon this first.

On Tue, May 30, 2023 at 4:35 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Sun, 28 May 2023 23:07:40 +0300
> Baruch Even <baruch@weka.io> wrote:
>
> > Hi,
> >
> > We found an issue with newer kernels (5.13+) that are found on newer OSes
> > (Ubuntu22, Rocky9, Ubuntu20 with kernel 5.15) where a 2M page that was
> > allocated for DPDK was migrated (moved into another physical page) when a
> > 1G page was allocated.
> >
> > From our reading of the kernel commits this started with commit
> > ae37c7ff79f1f030e28ec76c46ee032f8fd07607
> >     mm: make alloc_contig_range handle in-use hugetlb pages
> >
> > This caused what looked like memory corruptions to us and cases where the
> > rings were moved from their physical location and communication was no
> > longer possible.
> >
> > I wanted to ask if anyone else hit this issue and what mitigations are
> > available?
> >
> > We are currently looking at using a kernel driver to pin the pages but I
> > expect that this issue will affect others and that a more general
> approach
> > is needed.
> >
> > Thanks,
> > Baruch
> >
>
> Fix might be as simple as asking kernel to lock the mmap().
>
> diff --git a/lib/eal/linux/eal_hugepage_info.c
> b/lib/eal/linux/eal_hugepage_info.c
> index 581d9dfc91eb..989c69387233 100644
> --- a/lib/eal/linux/eal_hugepage_info.c
> +++ b/lib/eal/linux/eal_hugepage_info.c
> @@ -48,7 +48,8 @@ map_shared_memory(const char *filename, const size_t
> mem_size, int flags)
>                 return NULL;
>         }
>         retval = mmap(NULL, mem_size, PROT_READ | PROT_WRITE,
> -                       MAP_SHARED, fd, 0);
> +                       MAP_SHARED_VALIDATE | MAP_LOCKED, fd, 0);
> +
>         close(fd);
>         return retval == MAP_FAILED ? NULL : retval;
>  }
>


-- 
Baruch Even
Platform Technical Lead,  WEKA
E baruch@weka.io* ­*W www.weka.io
<https://www.weka.io?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature>*
­* * ­*
<https://www.weka.io/lp/weka-named-a-2023-customers-choice-by-gartner-peer-insights/?utm_source=signature&utm_medium=email>

[-- Attachment #2: Type: text/html, Size: 6402 bytes --]

  reply	other threads:[~2023-05-30 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 20:07 Baruch Even
2023-05-30  1:35 ` Stephen Hemminger
2023-05-30 13:51   ` Baruch Even [this message]
2023-05-30  3:11 ` Stephen Hemminger
2023-05-30  8:04 ` Bruce Richardson
2023-05-30 13:53   ` Baruch Even
2023-05-30 15:33     ` 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='CAKye4QY0p-sni0X0Ly6WS=qtwqZ=twj7X_Rvu5U2e8WMsmzeZw@mail.gmail.com' \
    --to=baruch@weka.io \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).