From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id DC45C156 for ; Fri, 29 Nov 2013 06:54:20 +0100 (CET) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id D623136B37; Fri, 29 Nov 2013 11:25:02 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id BE70F36B2D; Fri, 29 Nov 2013 11:25:02 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Fri, 29 Nov 2013 11:25:02 +0530 From: Prashant Upadhyaya To: Stephen Hemminger Date: Fri, 29 Nov 2013 11:25:01 +0530 Thread-Topic: [dpdk-dev] Regarding VM live migration with SRIOV Thread-Index: Ac7rOUNmjP/aHj5ORr+TL5bl5SyTTgBja9nw Message-ID: References: <20131126204554.4b3f9c93@nehalam.linuxnetplumber.net> <20131126222411.41d0e8fd@nehalam.linuxnetplumber.net> In-Reply-To: <20131126222411.41d0e8fd@nehalam.linuxnetplumber.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: No Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Regarding VM live migration with SRIOV X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2013 05:54:21 -0000 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 fin= d out that the PCI device on which it was doing the I/O has been removed fr= om underneath. In that case the application can call the ethdev stop and et= hdev 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 d= evice 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 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 d= oes the application now know that the device is gone ? > > Is it that rte_eal_pci_probe should be called periodically from, let's sa= y, 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 laye= r. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D