From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Wed, 11 Jul 2018 17:46:09 +0200 (CEST) Received: by mail-pg1-f196.google.com with SMTP id n15-v6so3022930pgv.4 for ; Wed, 11 Jul 2018 08:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=jaG88JadWKuTR9CMSvar56MoOCXyRoj6gNpxRBo0AsM=; b=S6xCzeZgSxjqXGWalPqPzVUwSfNRF2l60bG/f02Vr5lUAPC5BvPQAkEJ2TzwOiZuBa naQeUXOVyKZjIY4CzCUCLjWfUEe/ZLqSLEQQdjKbsckteV5bBi42/XUV1dN13Nz8xsnV 7jFTT2i/Y3jQpws1zIjYfiqDavp8BjWCP114Sm11VrqMGe+BhAxy/AyQLlsKBZ/Igb8w Uz+7m7TdN7XiCU0+H3KWNIUq8kZahFlQDJ1GAXN3DByDL7SMDMxKnaXmT+JdqPE/62j7 RZuFaKoUEDGQWrxuAlEo0lwpuURO4fHcjqiZWpkKe4X69pF1w8XaOje3F5eV1CT4Lxvv wsUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=jaG88JadWKuTR9CMSvar56MoOCXyRoj6gNpxRBo0AsM=; b=ZAT8DnvYn+AYF7dx4P09Ww+302fnOJzgSKBEHQ3+tDZegH99Ypr1zQKyNoqZgGVBZ1 6SIYmnHo7CEBgkBgZwvaMtrskBE793wMZizd53Au80RsnRbvujTwZdy74lesJCkO+ni1 Zbe6YuDKItci982MGOtAwI+Pi4F4j18vTbiKWPTGVmM9WAVyrb9NUGKN2p88+pkcHoTC douy+1Sk58eECvYJ4U/Tyr80GxF2B7s1jk+n+HCZ3022ogyaxnUoZpZ5R/Ne9VF/qwDT lIi/k2t5saJ+u+4V1NBa573OV76G5eGlQDq0EEMzjzl0bTHFP8xU63I5z2o6iaAcb8VR 6UcQ== X-Gm-Message-State: APt69E18TeVabzIS8PiCrxQd6Hl6UyhHXWdU26RvDMVIk0uSXpWuyH/E VqVmBfNeIBmyVBgXsKqaExSUYg== X-Google-Smtp-Source: AAOMgpf2g62Xbbc8peqny11Ku2Tni2WBRKqB/LjOuZufW1K3gweJHP7QHXnv5Ou+mw76IY80AywphQ== X-Received: by 2002:a62:2785:: with SMTP id n127-v6mr30782125pfn.129.1531323968420; Wed, 11 Jul 2018 08:46:08 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id l25-v6sm4580380pff.8.2018.07.11.08.46.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 11 Jul 2018 08:46:08 -0700 (PDT) Date: Wed, 11 Jul 2018 08:46:04 -0700 From: Stephen Hemminger To: Jeff Guo 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 Message-ID: <20180711084604.61cb5eea@xeon-e3> In-Reply-To: <1531305717-15504-1-git-send-email-jia.guo@intel.com> 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 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: Wed, 11 Jul 2018 15:46:09 -0000 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 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.