From: sujith sankar <sujithsankar2@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] IXGBE VF on KVM - Transmit stalled after switch reboot
Date: Mon, 22 Jan 2018 16:26:53 +0530 [thread overview]
Message-ID: <CAMTiEwe3ajCUXYcd8gZf3kJ5t4=Gbbg36ydGv28tt2i0qwuVZg@mail.gmail.com> (raw)
Hi,
We are seeing a stall in packet transmission from VF after a network
switch (Nexus 9000) restart. The packets sent out on ixgbe-vf are not
seen on the wire. Is this expected when the switch restarts? Is a
re-init of VF expected from PMD?
The application, which is based on DPDK 16.04, is running inside an
Ubuntu VM on KVM. It uses a VF that has been passed through to the VM
and the PF is owned by Linux kernel mode driver.
PF is able to transmit packets. VFs that are inside the VM and that
are not claimed by DPDK are also working fine. I feel that there is a
recovery sequence that is expected from the application/PMD in such a
case.
It would be great if IXGBE PMD maintainers or someone who is familiar
with this could help us. Kindly let me know if you have questions.
Thanks,
-Sujith Sankar
Avi Networks (India) Pvt Ltd.
reply other threads:[~2018-01-22 10:56 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='CAMTiEwe3ajCUXYcd8gZf3kJ5t4=Gbbg36ydGv28tt2i0qwuVZg@mail.gmail.com' \
--to=sujithsankar2@gmail.com \
--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).