From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id AF63F44BE for ; Wed, 24 Oct 2018 21:57:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 50FDF2201E; Wed, 24 Oct 2018 15:57:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 24 Oct 2018 15:57:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=iGsAvHlR8diyGoqkGMu3Vwaditgr+f/FHf6JkUUl3bM=; b=nYCMGrSNvHxM SXvF9jQFq+9vPaRHqyvZRowmbV3l3DdxNGYr0B4D7xswOLAfayaIEMO4Ld9YK8vN 3nR9xvI28Txcgrmya8yQDXjBw6kdv7G2CY6Erv5tHOeBVfltXAu7t8aAqtwtLCBj GxuKiG1R3MHhr2t6enJPR5nOSTYl8Ic= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=iGsAvHlR8diyGoqkGMu3Vwaditgr+f/FHf6JkUUl3 bM=; b=ZO7XOhOzJ5byAxuMWhYzyH5rgVCJOB4kMPHMAb/WThy/z9zvKSqiVxCML s+p5PJ3huzjajaLzWbQKS7aY2CQpKmVkzWjK7q5HKfEdwh8WPG6BQ2UipOx9Vx7j G1ZDXUwt8YM98jUsv+lBtrIp/s/zId32UkWKAGdpYcvDgAEXT4yCcmlS/qa0lqni 1OoZjbfrrv40lvrSytanOuBlSPyToiu9dNsTq1YnFz5ADEomqOGW99o6sevXOkKb jtWkU6kXDQo16IZtLDhKw0FIx6ctYHkeTwsz/SzP4FeFHOPGc1kss+Xvtp2FsKDL C5BgJdEcSxXwq/P5oIplWmfXlzchg== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B5461E40E6; Wed, 24 Oct 2018 15:57:45 -0400 (EDT) From: Thomas Monjalon To: "Iremonger, Bernard" Cc: "Wu, Jingjing" , "Lu, Wenzhuo" , "dev@dpdk.org" , "ophirmu@mellanox.com" , "wisamm@mellanox.com" , "Yigit, Ferruh" , "arybchenko@solarflare.com" Date: Wed, 24 Oct 2018 21:57:48 +0200 Message-ID: <1592659.ocTt40gUXr@xps> In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D17043@IRSMSX107.ger.corp.intel.com> References: <20181024134111.26771-1-thomas@monjalon.net> <20181024134111.26771-6-thomas@monjalon.net> <8CEF83825BEC744B83065625E567D7C260D17043@IRSMSX107.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 5/5] app/testpmd: setup attached ports on probe event 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, 24 Oct 2018 19:57:47 -0000 24/10/2018 18:13, Iremonger, Bernard: > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > +set port setup on > > +~~~~~~~~~~~~~~~~~ > > + > > +Select how to retrieve new ports created after "port attach" command. > > + > > +For each new port, a setup is done. > > +It will find the probed ports via RTE_ETH_FOREACH_MATCHING_DEV loop in > > +iterator mode, or via RTE_ETH_EVENT_NEW in event mode. > > + > > It would be useful to add an example command here (similar to other commands). Do you mean something like this? testpmd> set port setup on (iterator|event)