DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1657] Unsuitable IOVA mode may be picked as the default
Date: Mon, 03 Feb 2025 04:35:38 +0000	[thread overview]
Message-ID: <bug-1657-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1657
           Summary: Unsuitable IOVA mode may be picked as the default
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

Not all kernel drivers and not all devices support all IOVA modes. EAL will
attempt to pick a reasonable default based on a number of factors, but there
may be cases where the default may be unsuitable (for example, hotplugging
devices using igb_uio driver while having picked IOVA as VA mode on EAL
initialization).

Implication
Some devices (hotplugged or otherwise) may not work due to incompatible IOVA
mode being automatically picked by EAL.

Resolution/Workaround:
It is possible to force EAL to pick a particular IOVA mode by using the
–iova-mode command-line parameter. If conflicting requirements are present
(such as one device requiring IOVA as PA and one requiring IOVA as VA mode),
there is no workaround.

Affected Environment/Platform:
Linux.

Driver/Module:
ALL.

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

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

                 reply	other threads:[~2025-02-03  4:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1657-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 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).