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: Fri, 29 Nov 2013 11:25:01 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF21A0@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <20131126222411.41d0e8fd@nehalam.linuxnetplumber.net>
Hi Stephen,
Agreed that the current code does not directly support hotplug.
Now I am looking for a hint regarding how best the DPDK application can find out that the PCI device on which it was doing the I/O has been removed from underneath. In that case the application can call the ethdev stop and ethdev close functions gracefully.
Question is -- is there a way for the PMD to know that the device is gone.
Further the PCI device is a mapped memory, so when the plugout of the PCI device happen, is the DPDK application, which is doing I/O, vulnerable to a crash ?
Regards
-Prashant
-----Original Message-----
From: Stephen Hemminger [mailto:stephen@networkplumber.org]
Sent: Wednesday, November 27, 2013 11:54 AM
To: Prashant Upadhyaya
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding VM live migration with SRIOV
On Wed, 27 Nov 2013 11:39:28 +0530
Prashant Upadhyaya <prashant.upadhyaya@aricent.com> wrote:
> 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
>
Like I said current code doesn't do hotplug.
If you wanted to add it, you would have to refactor the PCI management layer.
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
prev parent reply other threads:[~2013-11-29 5:54 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
2013-11-27 6:24 ` Stephen Hemminger
2013-11-29 5:55 ` Prashant Upadhyaya [this message]
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=C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF21A0@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).