From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id EA22E1CD88 for ; Thu, 5 Apr 2018 23:48:27 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7A4F720DDC; Thu, 5 Apr 2018 17:48:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 05 Apr 2018 17:48:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=XB/yM1sCN6lp5qbl67MvUtoM48 +ekd1+4kSeyxDSALs=; b=V9SepbGE7yPCE8xq+EcrxLm54Yo7iHBnVLJly7MCKa Aale2XxvMHU9zxDxPa3Zme8fPDISLRc768R+YS6eeHwoaMSjQUDVqWbxwY/WCWly LcSoeWjgKkZpHGCSq5l+DKAtbOYA62x8pb93wDt5DLyAm1GWDqVkLRql/jBArT0h c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=XB/yM1 sCN6lp5qbl67MvUtoM48+ekd1+4kSeyxDSALs=; b=BNeLD3tgwISnti4eZZY4SE 4yXK1aNc9ZEbTeLMaysN8FYAoQ6PRTQU3GKbQIQeS0/mf8kobtnIve5cc3YcuUYn N8txU9FfzSMS+htTA+pYSHK5Ga3UsFWidrpJ5GR/gp8oPsRZ9cWSdgB6f89qZPyg fcM2HUp+MgOXeZpv8otNBT8t5bfedssskhbO9SwIN6O6H+s+C8YmaKK0PAk1Fmeq r3FwHWVO8Zx3Z7DbZlR736PZm6nVS4mXY6591zXOnr5kkEftz6EpVEUwdKGTGd0p nxp3+5puuwVCP+r7GeMvUUlto+JHG6jzPcQSzUnAPyW6OMqBtcwRVWI0mpbO26SQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 01026E4437; Thu, 5 Apr 2018 17:48:25 -0400 (EDT) From: Thomas Monjalon To: Jeff Guo , shreyansh.jain@nxp.com Cc: stephen@networkplumber.org, bruce.richardson@intel.com, ferruh.yigit@intel.com, konstantin.ananyev@intel.com, gaetan.rivet@6wind.com, jingjing.wu@intel.com, motih@mellanox.com, harry.van.haaren@intel.com, jianfeng.tan@intel.com, dev@dpdk.org, helin.zhang@intel.com Date: Thu, 05 Apr 2018 23:48:25 +0200 Message-ID: <3928106.ZGSgniU5kR@xps> In-Reply-To: <1522944617-16601-5-git-send-email-jia.guo@intel.com> References: <1522918968-15290-5-git-send-email-jia.guo@intel.com> <1522944617-16601-1-git-send-email-jia.guo@intel.com> <1522944617-16601-5-git-send-email-jia.guo@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH V20 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: Thu, 05 Apr 2018 21:48:28 -0000 05/04/2018 18:10, Jeff Guo: > Use testpmd for example, to show how an application uses device event > APIs to monitor the hotplug events, including both hot removal event > and hot insertion event. > > The process is that, testpmd first enable hotplug by below commands, > > E.g. ./build/app/testpmd -c 0x3 --n 4 -- -i --hot-plug I am not convinced by the testpmd option. Why not just a CLI command to start monitoring events?