From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 6C2D21B526 for ; Thu, 12 Jul 2018 05:14:39 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jul 2018 20:14:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,341,1526367600"; d="scan'208";a="239675910" Received: from jguo15x-mobl3.ccr.corp.intel.com (HELO [10.67.68.64]) ([10.67.68.64]) by orsmga005.jf.intel.com with ESMTP; 11 Jul 2018 20:14:32 -0700 To: Stephen Hemminger References: <1498711073-42917-1-git-send-email-jia.guo@intel.com> <1531305717-15504-1-git-send-email-jia.guo@intel.com> <20180711084604.61cb5eea@xeon-e3> Cc: bruce.richardson@intel.com, ferruh.yigit@intel.com, konstantin.ananyev@intel.com, gaetan.rivet@6wind.com, jingjing.wu@intel.com, thomas@monjalon.net, motih@mellanox.com, matan@mellanox.com, harry.van.haaren@intel.com, qi.z.zhang@intel.com, shaopeng.he@intel.com, bernard.iremonger@intel.com, arybchenko@solarflare.com, wenzhuo.lu@intel.com, jblunck@infradead.org, shreyansh.jain@nxp.com, dev@dpdk.org, helin.zhang@intel.com From: Jeff Guo Message-ID: Date: Thu, 12 Jul 2018 11:14:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20180711084604.61cb5eea@xeon-e3> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v9 0/7] hotplug failure handle mechanism X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 03:14:41 -0000 On 7/11/2018 11:46 PM, Stephen Hemminger wrote: > On Wed, 11 Jul 2018 18:41:50 +0800 > Jeff Guo wrote: > >> As we know, hot plug is an importance feature, either use for the datacenter >> device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring >> the higher flexibility and continuality to the networking services in multiple >> use cases in industry. So let we see, dpdk as an importance networking >> framework, what can it help to implement hot plug solution for users. >> >> We already have a general device event detect mechanism, failsafe driver, >> bonding driver and hot plug/unplug api in framework, app could use these to >> develop their hot plug solution. > I like seeing a better solution to hot plug. But it is worth mentioning > that for the Hyper-V netvsc driver this is mostly unnecessary. The Hyper-V > host notifies the network driver directly about availability of SRIOV > device, and the netvsc device driver can use that to do its own VF > management. It doesn't really need (or want) to be using a general > PCI solution. I am not sure about Hyper-v netvsc driver, but i am very interesting to deep analyze it to find what could let we find a best solution for hotplug. But since some customer, who like me still not have chance to use Hyper-v, they will encounter the hotplug issue when use kvm or other platform. so let we said that the topic about here is aim to fix the issue for that part of customer or developer. Just let hotplug be used more in diversity scenario.