From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 5142E1CA80 for ; Fri, 6 Apr 2018 05:51:39 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Apr 2018 20:51:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,413,1517904000"; d="scan'208";a="214352090" Received: from jguo15x-mobl3.ccr.corp.intel.com (HELO [10.67.68.27]) ([10.67.68.27]) by orsmga005.jf.intel.com with ESMTP; 05 Apr 2018 20:51:35 -0700 To: Thomas Monjalon , shreyansh.jain@nxp.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> <3928106.ZGSgniU5kR@xps> 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 From: "Guo, Jia" Message-ID: <64dd2d06-9463-02f5-eeeb-9219f01455a7@intel.com> Date: Fri, 6 Apr 2018 11:51:35 +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: <3928106.ZGSgniU5kR@xps> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 06 Apr 2018 03:51:39 -0000 On 4/6/2018 5:48 AM, Thomas Monjalon wrote: > 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? hot plug is a basic related memory like feature, let the feature go into option like other base option would be make sense i think. >