From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f172.google.com (mail-pf0-f172.google.com [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id 6E4C92B98 for ; Tue, 19 Jul 2016 04:48:50 +0200 (CEST) Received: by mail-pf0-f172.google.com with SMTP id p64so2189126pfb.1 for ; Mon, 18 Jul 2016 19:48:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igel-co-jp.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=DKvAtC1bKRB2c250m+96j0xEqZEq2Eki+IXmypOu0wA=; b=aWzkzPlH90yfiopPgF6lwFREpeKNoUeYLIApPCmOKjKIqN2rW4KuqZ71q7khO1zvz4 xgAXup1on1Zs85piJH+/QIE5KRjxhdlfmNUdIucL62UdbWg8gzWjSgQ+9KgYkLzP0AEO YhkR+sj597LltRWnLdIzTMIhG/AoZusXsfGuEDHyyeIOo8fTb0KBXU+r35Sdb65fZweg fYbR5naQzO4559RPpzrB2jMK7WykC27a0eQSEpx4SjNAIhPm03KBGGeftJBPy6vRkzn/ o0h/0FGwK8rkuNiIotCxOV6q8NL0MOYcfdV0Havc7Fzp/+uHm62mJ5XDxosJu2imfWWb sV2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=DKvAtC1bKRB2c250m+96j0xEqZEq2Eki+IXmypOu0wA=; b=nNsfYcYMPvRzAwVkJd5448mtWqwQZZVwz4ZG2oWD7ULnnE4gBl+ycWkcX/uNjJ7e52 IsfhasvGwMU7PUvfpJeprw2eSJXI7zxvwi5VcEbmSiUDdf0cPUmxclPJRxDRYI5uS3jO yRrj435c+PfjW0YCYg7kWPzCuGIJjPNMOeDolSFs6GgOYmBqEu7xsUbHgUww4h1qlYPz sKpvr7K5RcV7tdmSPhPI+a/WMX6VcLBO7emN/BuDs+muLQ6pfyfG7Al4u5eGsr+Vl+is /3LrHfhCiktmltqkc5L+zSyTaVKPq2/i6dcU9k0he8/V993D6a10Rz8l8H88XC4Sz6R8 n3jg== X-Gm-Message-State: ALyK8tKJ+42HGn0mTtpFhsxBt1ZMqBb7wHE7ieHp0Y27hRxZFfTo5Y2kfMstAx+HefZ8j7bO X-Received: by 10.98.57.90 with SMTP id g87mr51339732pfa.106.1468896529713; Mon, 18 Jul 2016 19:48:49 -0700 (PDT) Received: from [192.168.1.4] (p5221004-ipngn11502marunouchi.tokyo.ocn.ne.jp. [153.163.183.4]) by smtp.googlemail.com with ESMTPSA id w67sm406708pfw.41.2016.07.18.19.48.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 19:48:49 -0700 (PDT) To: Eli Britstein , "dev@dpdk.org" References: <8CEF83825BEC744B83065625E567D7C21A04F18C@IRSMSX108.ger.corp.intel.com> Cc: "Iremonger, Bernard" From: Tetsuya Mukawa Message-ID: <7be321ba-9eb7-2932-ae73-dc7a33b225e6@igel.co.jp> Date: Tue, 19 Jul 2016 11:48:50 +0900 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] SRIOV hot unplug 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: Tue, 19 Jul 2016 02:48:50 -0000 Hi Eli, On 2016/07/18 17:47, Eli Britstein wrote: > Hi Bernard, > > Thank you for your answer. > However, to do this, I have to have some communication protocol to the VM's application in order for it to do this sequence and acknowledge that it is now safe to proceed with detaching the device. > This implies some kind of integration from the host side, which I would like to avoid. I guess you should have some kind of communication channel to notice the hotpluging events from host to VM. > Do you think might there be any other way for the application to handle such event in a smooth way? So far, I guess having one more virtio-net device will be easiest way. Thanks, Tetsuya > > Thanks, > Eli > >> -----Original Message----- >> From: Iremonger, Bernard [mailto:bernard.iremonger@intel.com] >> Sent: Sunday, 17 July, 2016 11:53 PM >> To: Eli Britstein; dev@dpdk.org >> Cc: Iremonger, Bernard >> Subject: RE: SRIOV hot unplug >> >> 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. >>> ---------------------------------------------------------------------- >>> ------------------------ >>> -------------------------------------------------- > > ------------------------------------------------------------------------------------------------------------------------------------------------- > 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. > ------------------------------------------------------------------------------------------------------------------------------------------------ >