From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v3 1/2] app/test: fix failures in the ring_pmd_autotest program Date: Fri, 27 Nov 2015 16:14:46 +0000 Message-ID: <20151127161445.GB27472@bricha3-MOBL3> References: <1448640460-25249-1-git-send-email-bernard.iremonger@intel.com> <1448640460-25249-2-git-send-email-bernard.iremonger@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Bernard Iremonger Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 86E9C5685 for ; Fri, 27 Nov 2015 17:15:13 +0100 (CET) Content-Disposition: inline In-Reply-To: <1448640460-25249-2-git-send-email-bernard.iremonger@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Nov 27, 2015 at 04:07:39PM +0000, Bernard Iremonger wrote: > If eth_ring vdevs are created from the command line with the --vdev option, > they create there own rings which are not shared by other vdevs. Typo: s/their/there/ > Some of tests in this suite require that the vdevs share rings, so some > of the tests fail. > > For vdevs to share rings they must be created in the test code with the > rte_eth_from_rings() function using rings created with the rte_ring_create() > function. > > Use the command line option --vdev=eth_ring0 to create port 0. As I understand it, this option is not mandatory for the tests to pass, it only allows some additional functional tests on cmd-line created rings to be run. This should perhaps still be called out in the commit message. > Create two rings and five ethdevs in test_pmd_ring.c for ports 1 to 5. "... and then use these to run the unit tests on the pmd ring functionality" > Improve test output by adding the port number to printf statements, > and adding a printf describing each test. > /Bruce