dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Prashant Upadhyaya
	<prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Regarding VM live migration with SRIOV
Date: Tue, 26 Nov 2013 22:24:11 -0800	[thread overview]
Message-ID: <20131126222411.41d0e8fd@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1DED-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>

On Wed, 27 Nov 2013 11:39:28 +0530
Prashant Upadhyaya <prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org> 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.

  parent reply	other threads:[~2013-11-27  6:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 14:01 Regarding VM live migration with SRIOV Prashant Upadhyaya
     [not found] ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1B53-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-27  4:39   ` Prashant Upadhyaya
     [not found]     ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1DB6-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-27  4:45       ` Stephen Hemminger
     [not found]         ` <20131126204554.4b3f9c93-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-11-27  6:09           ` Prashant Upadhyaya
     [not found]             ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF1DED-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-27  6:24               ` Stephen Hemminger [this message]
     [not found]                 ` <20131126222411.41d0e8fd-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
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=20131126222411.41d0e8fd@nehalam.linuxnetplumber.net \
    --to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=prashant.upadhyaya-pccXkzZloW5BDgjK7y7TUQ@public.gmane.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).