All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1628] Multi-process sample app requires exact memory mapping
Date: Mon, 03 Feb 2025 02:40:46 +0000	[thread overview]
Message-ID: <bug-1628-3@http.bugs.dpdk.org/> (raw)

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

https://bugs.dpdk.org/show_bug.cgi?id=1628

            Bug ID: 1628
           Summary: Multi-process sample app requires exact memory mapping
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

The multi-process example application assumes that it is possible to map the
hugepage memory to the same virtual addresses in client and server
applications. Occasionally, very rarely with 64-bit, this does not occur and a
client application will fail on startup. The Linux “address-space layout
randomization” security feature can sometimes cause this to occur.

Implication:
A multi-process client application fails to initialize.

Resolution/Workaround:
See the “Multi-process Limitations” section in the DPDK Programmer’s Guide for
more information.

Affected Environment/Platform:
All.

Driver/Module:
Multi-process example application

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

             reply	other threads:[~2025-02-03  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  2:40 bugzilla [this message]
2025-02-03  4:18 ` [DPDK/examples Bug 1628] Multi-process sample app requires exact memory mapping bugzilla

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=bug-1628-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.