From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Eli Britstein <eli.britstein@toganetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] SRIOV hot unplug
Date: Sun, 17 Jul 2016 20:53:29 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C21A04F18C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <VI1PR02MB1727F927CE6AC248C3F4AA6383350@VI1PR02MB1727.eurprd02.prod.outlook.com>
Hi Eli,
The DPDK application in the VM should remove the slave device from the bond device, stop, close and detach the device in the VM before doing "virsh detach-device" from the host.
Regards,
Bernard.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Eli Britstein
> Sent: Sunday, July 17, 2016 9:58 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] SRIOV hot unplug
>
> Hello,
>
> A DPDK application with a DPDK bond device, with 2 slaves: one vnic, and
> another is a SRIOV VF connected as a pathrough.
> The bond device is configured as ACTIVE/BACKUP, and the primary is the VF
> slave.
> Now, I do "virsh detach-device" from the host, and the DPDK process in the
> VM gets segmentation fault, as it tries to poll an address that is not mmaped
> anymore.
> I wonder if this flow is supposed to be supported by DPDK, or not.
> Please advise.
>
> Thanks,
> Eli
> ----------------------------------------------------------------------------------------------
> ---------------------------------------------------
> This email and any files transmitted and/or attachments with it are
> confidential and proprietary information of Toga Networks Ltd., and
> intended solely for the use of the individual or entity to whom they are
> addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information of Toga Networks Ltd., and is
> intended only for the individual named. If you are not the named addressee
> you should not disseminate, distribute or copy this e-mail. Please notify the
> sender immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this information is strictly prohibited.
> ----------------------------------------------------------------------------------------------
> --------------------------------------------------
next prev parent reply other threads:[~2016-07-17 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 8:58 Eli Britstein
2016-07-17 20:53 ` Iremonger, Bernard [this message]
2016-07-18 8:47 ` Eli Britstein
2016-07-19 2:48 ` Tetsuya Mukawa
2016-07-19 11:18 ` Eli Britstein
2016-07-19 14:14 ` Declan Doherty
2016-07-19 14:34 ` Eli Britstein
2016-07-20 8:59 ` Eli Britstein
2016-07-20 5:16 ` Tetsuya Mukawa
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=8CEF83825BEC744B83065625E567D7C21A04F18C@IRSMSX108.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=eli.britstein@toganetworks.com \
/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).