From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 33C9E2BA7 for ; Thu, 3 May 2018 10:58:36 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 May 2018 01:58:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,357,1520924400"; d="scan'208";a="47960853" Received: from jeffguo-z170x-ud5.sh.intel.com (HELO localhost.localdomain) ([10.67.104.10]) by orsmga003.jf.intel.com with ESMTP; 03 May 2018 01:58:31 -0700 From: Jeff Guo To: stephen@networkplumber.org, 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, jianfeng.tan@intel.com Cc: jblunck@infradead.org, shreyansh.jain@nxp.com, dev@dpdk.org, jia.guo@intel.com, helin.zhang@intel.com Date: Thu, 3 May 2018 16:57:05 +0800 Message-Id: <1525337829-3893-1-git-send-email-jia.guo@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1498711073-42917-1-git-send-email-jia.guo@intel.com> References: <1498711073-42917-1-git-send-email-jia.guo@intel.com> Subject: [dpdk-dev] [PATCH V21 0/4] hot plug recovery 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, 03 May 2018 08:58:36 -0000 At the prior, device event monitor framework have been introduced, the typical usage is for device hot plug. If we want application would not be break down when device hot plug in or out, we still need some measures to help app to handle that, such as recovery device for device detaching, so that app can keep running smoothly but not be disturbed by any hotplug behaviors. This patch set will introduces an recovery mechanism to handle hot unplug, and also use testpmd to show example of how to use this mechanism to process hot plug event. The process could be shown as below: plug out->failure handle->stop forward->stop port->close port->detach port with this mechanism, user such as fail-safe driver or testpmd could be able to develop their own hot plug application. patchset history: v21->v20: split function in hot unplug ops sync failure hanlde to fix multiple process issue fix attach port issue for multiple devices case. v20->v19: clean the code refine the remap logic for multiple device. remove the auto binding v19->18: note for limitation of multiple hotplug,fix some typo, sqeeze patch. v18->v15: add document, add signal bus handler, refine the code to be more clear. the prior patch history please check the patch set "add device event monitor framework" Jeff Guo (4): bus/pci: handle device hot unplug eal: add failure handle mechanism for hot plug igb_uio: fix uio release issue when hot unplug app/testpmd: show example to handle hot unplug app/test-pmd/testpmd.c | 28 ++++-- drivers/bus/pci/pci_common.c | 65 ++++++++++++++ drivers/bus/pci/pci_common_uio.c | 33 +++++++ drivers/bus/pci/private.h | 12 +++ kernel/linux/igb_uio/igb_uio.c | 4 + lib/librte_eal/common/include/rte_bus.h | 16 ++++ lib/librte_eal/linuxapp/eal/eal_dev.c | 154 +++++++++++++++++++++++++++++++- 7 files changed, 306 insertions(+), 6 deletions(-) -- 2.7.4