From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v9 0/7] hotplug failure handle mechanism
Date: Wed, 11 Jul 2018 08:46:04 -0700
Message-ID: <20180711084604.61cb5eea@xeon-e3>
References: <1498711073-42917-1-git-send-email-jia.guo@intel.com>
 <1531305717-15504-1-git-send-email-jia.guo@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
To: Jeff Guo <jia.guo@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pg1-f196.google.com (mail-pg1-f196.google.com
 [209.85.215.196]) by dpdk.org (Postfix) with ESMTP id 429A11B432
 for <dev@dpdk.org>; Wed, 11 Jul 2018 17:46:09 +0200 (CEST)
Received: by mail-pg1-f196.google.com with SMTP id n15-v6so3022930pgv.4
 for <dev@dpdk.org>; Wed, 11 Jul 2018 08:46:09 -0700 (PDT)
In-Reply-To: <1531305717-15504-1-git-send-email-jia.guo@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, 11 Jul 2018 18:41:50 +0800
Jeff Guo <jia.guo@intel.com> wrote:

> As we know, hot plug is an importance feature, either use for the datacen=
ter
> device=E2=80=99s fail-safe, or use for SRIOV Live Migration in SDN/NFV. I=
t could bring
> the higher flexibility and continuality to the networking services in mul=
tiple
> 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.
>=20
> 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.