From: madhukar mythri <madhukar.mythri@gmail.com>
To: users <users@dpdk.org>
Subject: Seg-fault crash with the VF removal on Azure VM
Date: Mon, 30 Jun 2025 22:04:01 +0530 [thread overview]
Message-ID: <CAAUNki29b-sJjMQnut4OSWqMp8UdFULa52-DVVrwszQcUv6svg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi,
We are facing a Seg-fault crash issue on our DPDK application with
"failsafe" PMD on Azure VM, when we toggle the Azure "Accelerated
networking" option.
On the running VM, when we toggle(disable/enable) the "Accelerated
networking" option, then we could see the respective SRIOV VF device was
removed and added back, at this time our DPDK application got crashed while
doing Rx "failsafe_rx_burst_fast()" operation.
As per the DPDK "failsafe" PMD design the hotplug is supported and even
after the primary SRIOV VF device is removed, the application can run Rx/Tx
operations seamlessly on the other sub-device("netvsc"). But, this is not
happening.
Does anybody tested this hot-plug functionality on Azure VM and hot-plug
works well on DPDK apps ?
Any known issues/limitations on the "failsafe" PMD hot-plug ?
DPDK-version: 23.11
Linux kernel-version: 5.15.0
Thanks,
Madhukar.
[-- Attachment #2: Type: text/html, Size: 6412 bytes --]
reply other threads:[~2025-06-30 16:34 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=CAAUNki29b-sJjMQnut4OSWqMp8UdFULa52-DVVrwszQcUv6svg@mail.gmail.com \
--to=madhukar.mythri@gmail.com \
--cc=users@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).