From: Wei Hu <weh@microsoft.com>
To: dev@dpdk.org, stephen@networkplumber.org, stable@dpdk.org
Cc: longli@microsoft.com, weh@microsoft.com
Subject: [PATCH 0/2] net/mana: add device reset support for service events
Date: Wed, 29 Apr 2026 01:49:53 -0700 [thread overview]
Message-ID: <20260429084955.39164-1-weh@microsoft.com> (raw)
This series adds support for handling hardware service reset events
in the MANA and netvsc drivers.
When the MANA kernel driver receives a hardware service event, it
initiates a device reset and notifies userspace via
IBV_EVENT_DEVICE_FATAL. The MANA PMD handles this by performing an
automatic teardown and recovery sequence, using ethdev recovery
events (ERR_RECOVERING, RECOVERY_SUCCESS, RECOVERY_FAILED) to
notify upper layers.
Patch 1 implements the reset logic in the MANA driver, including
RCU-based data path quiescence, multi-process doorbell remap via
IPC, and a control thread for the recovery sequence.
Patch 2 adds recovery event handlers in the netvsc driver so it
can switch the data path to synthetic during reset and back to VF
after successful recovery.
Long Li (1):
net/netvsc: handle VF recovery events for service reset
Wei Hu (1):
net/mana: add device reset support
drivers/net/mana/mana.c | 924 ++++++++++++++++++++++++++++++++---
drivers/net/mana/mana.h | 33 +-
drivers/net/mana/meson.build | 2 +-
drivers/net/mana/mp.c | 89 +++-
drivers/net/mana/mr.c | 6 +-
drivers/net/mana/rx.c | 24 +-
drivers/net/mana/tx.c | 40 +-
drivers/net/netvsc/hn_vf.c | 106 ++++
8 files changed, 1121 insertions(+), 103 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-29 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 8:49 Wei Hu [this message]
2026-04-29 8:49 ` [PATCH 1/2] net/mana: add device reset support Wei Hu
2026-04-29 8:49 ` [PATCH 2/2] net/netvsc: handle VF recovery events for service reset Wei Hu
2026-04-29 14:56 ` 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=20260429084955.39164-1-weh@microsoft.com \
--to=weh@microsoft.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stable@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