From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/netuio Bug 1650] igb_uio can not be used when running l3fwd-power
Date: Mon, 03 Feb 2025 04:18:29 +0000 [thread overview]
Message-ID: <bug-1650-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1650
Bug ID: 1650
Summary: igb_uio can not be used when running l3fwd-power
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: netuio
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
Link Status Change(LSC) interrupt and packet receiving interrupt are all
enabled in l3fwd-power APP. Because of UIO only support one interrupt, so these
two kinds of interrupt need to share one, and the receiving interrupt have the
higher priority, so can’t get the right link status.
Implication:
When insmod igb_uio and running l3fwd-power APP, link status getting doesn’t
work properly.
Resolution/Workaround:
Use vfio-pci when LSC and packet receiving interrupt enabled.
Affected Environment/Platform:
ALL.
Driver/Module:
igb_uio module.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2998 bytes --]
reply other threads:[~2025-02-03 4:18 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-1650-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).