From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A52D25F2B for ; Mon, 2 Apr 2018 06:18:20 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Apr 2018 21:18:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,393,1517904000"; d="scan'208";a="47190024" Received: from jguo15x-mobl3.ccr.corp.intel.com (HELO [10.67.68.69]) ([10.67.68.69]) by orsmga002.jf.intel.com with ESMTP; 01 Apr 2018 21:18:16 -0700 To: Stephen Hemminger References: <1522063256-3997-5-git-send-email-jia.guo@intel.com> <1522339205-27698-1-git-send-email-jia.guo@intel.com> <1522339205-27698-5-git-send-email-jia.guo@intel.com> <20180329100059.0f10a32a@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, harry.van.haaren@intel.com, jianfeng.tan@intel.com, jblunck@infradead.org, shreyansh.jain@nxp.com, dev@dpdk.org, helin.zhang@intel.com From: "Guo, Jia" Message-ID: Date: Mon, 2 Apr 2018 12:18:16 +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: <20180329100059.0f10a32a@xeon-e3> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH V17 4/4] app/testpmd: enable device hotplug monitoring 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: Mon, 02 Apr 2018 04:18:21 -0000 On 3/30/2018 1:00 AM, Stephen Hemminger wrote: > On Fri, 30 Mar 2018 00:00:05 +0800 > Jeff Guo wrote: > >> Use testpmd for example, to show an application how to use device event >> mechanism to monitor the hotplug event, involve both hot removal event >> and the hot insertion event. >> >> The process is that, testpmd first enable hotplug monitoring and register >> the user's callback, when device being hotplug insertion or hotplug >> removal, the eal monitor the event and call user's callbacks, the >> application according their hot plug policy to detach or attach the device >> from the bus. >> >> Signed-off-by: Jeff Guo >> --- >> v17->v16: >> unregister all user's callback when stop event monitor >> --- >> app/test-pmd/parameters.c | 5 +- >> app/test-pmd/testpmd.c | 242 +++++++++++++++++++++++++++++++++++++++++++++- >> app/test-pmd/testpmd.h | 11 +++ >> 3 files changed, 256 insertions(+), 2 deletions(-) >> >> diff --git a/app/test-pmd/parameters.c b/app/test-pmd/parameters.c >> index 97d22b8..825d602 100644 >> --- a/app/test-pmd/parameters.c >> +++ b/app/test-pmd/parameters.c >> @@ -186,6 +186,7 @@ usage(char* progname) >> printf(" --flow-isolate-all: " >> "requests flow API isolated mode on all ports at initialization time.\n"); >> printf(" --tx-offloads=0xXXXXXXXX: hexadecimal bitmask of TX queue offloads\n"); >> + printf(" --hot-plug: enalbe hot plug for device.\n") > s/enalbe/enable/ will correct it.