From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Regarding VM live migration with SRIOV
Date: Wed, 27 Nov 2013 11:39:28 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1DED@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <20131126204554.4b3f9c93@nehalam.linuxnetplumber.net>
Hi Stephen,
The rte_eal_pci_probe is typically called at the startup.
Now let's say a DPDK application is running with a PCI device (doing tx and rx) and I remove that PCI device underneath (hot plugout)
So how does the application now know that the device is gone ?
Is it that rte_eal_pci_probe should be called periodically from, let's say, the slow control path of the DPDK application ?
Regards
-Prashant
-----Original Message-----
From: Stephen Hemminger [mailto:stephen@networkplumber.org]
Sent: Wednesday, November 27, 2013 10:16 AM
To: Prashant Upadhyaya
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding VM live migration with SRIOV
On Wed, 27 Nov 2013 10:09:09 +0530
Prashant Upadhyaya <prashant.upadhyaya@aricent.com> wrote:
> Hi,
>
> Let me be more specific.
> Does DPDK support hot plugin/plugout of PCI devices ?
> What typically needs to be done if this is to be achieved inside an application.
>
> Typically, the NIC PF or VF appears to the DPDK application as a PCI device which is probed at startup.
> Now what happens if I insert a new VF dynamically and want to use it
> inside the DPDK application (while it is already running), how should
> this typically be done ? [hotplugin] And what happens if the DPDK
> application is in control of a PCI device and that PCI device is
> suddenly removed ? How can the application detect this and stop doing
> data transfer on this and sort of unload it ? [hotplugout]
>
> If the above can be coded inside the DPDK app, then we can think of live VM migration with SRIOV -- just hotplugin and plugout the VF's.
>
> Regards
> -Prashant
>
The current implementation does look like it supports hotplug.
All devices are discovered during rte_eal_pci_probe.
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next prev parent reply other threads:[~2013-11-27 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 14:01 Prashant Upadhyaya
2013-11-27 4:39 ` Prashant Upadhyaya
2013-11-27 4:45 ` Stephen Hemminger
2013-11-27 6:09 ` Prashant Upadhyaya [this message]
2013-11-27 6:24 ` Stephen Hemminger
2013-11-29 5:55 ` Prashant Upadhyaya
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=C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1DED@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dev@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;
as well as URLs for NNTP newsgroup(s).