From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 996] DPDK:20.11.1: net/ena crash while fetching xstats
Date: Tue, 19 Apr 2022 20:35:32 +0000 [thread overview]
Message-ID: <bug-996-3-FHFc4PBMLu@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-996-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=996
Michal Krawczyk (mk@semihalf.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
CC| |mk@semihalf.com
--- Comment #1 from Michal Krawczyk (mk@semihalf.com) ---
Hi Amiya,
this is associated with lack of the proper MP support of the older ENA PMD (it
supports MP properly starting from DPDK v22.03).
The xstats API uses ENA admin queue in DPDK v20.11, and admin queue cannot be
used safely from the secondary process.
Those commits were improving the MP support starting from v20.11 to v22.03:
net/ena: make ethdev references multi-process safe
aab58857330bb4bd03f6699bf1ee716f72993774
net/ena: disable ops not supported by secondary process
39ecdd3dfa15d5ac591ce8d77d362480bff32355
net/ena: proxy AQ calls to primary process (this is the critical patch)
e3595539e0e03f0dbb81904f8edaaef0447a4f62
net/ena: enable stats for multi-process mode
3aa3fa851f58873457bdc5c387d0e5956f812322
net/ena/base: make IO memzone unique per port
850e1bb1c72b3d1163b2857ab7a02af11ba29c40
Thanks,
Michal
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-04-19 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 8:50 [Bug 996] PDK:20.11.1: " bugzilla
2022-04-19 20:35 ` bugzilla [this message]
2022-04-27 11:04 ` [Bug 996] DPDK:20.11.1: " bugzilla
2023-08-20 11:03 ` 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-996-3-FHFc4PBMLu@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).