From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gw2-out.broadcom.com (mail-gw2-out.broadcom.com [216.31.210.63]) by dpdk.org (Postfix) with ESMTP id EAD5D5A64 for ; Thu, 10 Sep 2015 06:25:24 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.17,501,1437462000"; d="scan'208";a="74679277" Received: from irvexchcas05.broadcom.com (HELO IRVEXCHCAS05.corp.ad.broadcom.com) ([10.9.208.26]) by mail-gw2-out.broadcom.com with ESMTP; 09 Sep 2015 21:49:56 -0700 Received: from IRVEXCHMB07.corp.ad.broadcom.com ([fe80::210e:9528:8c52:eb93]) by IRVEXCHCAS05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0235.001; Wed, 9 Sep 2015 21:25:22 -0700 From: Eric Kadison To: "'Liu, Yong'" , "dts@dpdk.org" Thread-Topic: Adding support for a new NIC on DTS Thread-Index: AdDlzlubNrQFUSIUQumZM9qZnXJpfgCbjvGAALmAlSA= Date: Thu, 10 Sep 2015 04:25:21 +0000 Message-ID: <7C99D44D787C8F4B9DC7D9BF9E6680541001591E@IRVEXCHMB07.corp.ad.broadcom.com> References: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com> <86228AFD5BCD8E4EBFD2B90117B5E81E10EE1BF3@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E10EE1BF3@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.208.64] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] Adding support for a new NIC on DTS X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2015 04:25:25 -0000 Hi Yong, Thank you for your reply. My execution.cfg contains: [Execution1] crbs=3D10.13.241.80 test_suites=3D # hello_world, # l3fwd jumboframes targets=3D x86_64-native-linuxapp-gcc parameters=3Dnic_type=3DBRCM57304:func=3Dtrue:perf=3Dfalse drivername=3Digb_uio Note that: - The DUT_PORT_MAP is built correctly. So the discovery process on the DU= T has found my NIC and discovered the correct connections to the Tester. T= he ports.cfg file has not been changed from its default. - The NIC is bound to our PMC correctly. This is clear in the output log.= At DTS completion, the kernel driver is reloaded properly. - As you can see, I have figured out that the "drivername" argument is req= uired and must contain the name of the uio driver. My settings.py file con= tains the driver name of the kernel driver for my NIC (not the PMD). - As you can see, I've tried the l3fwd and the jumboframes test suites. N= either works. The helloworld test was successful. - The l3fwd test performs setup and then runs no test cases. It appears t= hat DTS will only run the test cases if called out on the command line, tho= ugh I don't know why?? When I tried to add a test case function name to th= e command line, it still ran nothing. =20 - The jumboframes test executes, but reports errors. We are investigating= whether or not these errors might be actual errors in our PMD or NIC or th= e test case code, but other (non-DTS) tests for jumbo frames have passed. = The errors are on all the jumbo test cases (the nojumbo test case passes). = One test case fails with a Timeout on the "show port stats 0 " command. T= he log files and the test_results.xls file both show the passes and failure= s. A few questions: 1. Should we expect the jumboframes test case to pass with an arbitrary NIC= with a working PMD? 2. What is needed to make the l3fwd test case execute? 3. Can you suggest a test suite that should run without being customized t= o a specific NIC? 4. It appears that the conf directory contains a collection of configuratio= n files that may be needed under certain circumstances. Can you either def= ine when these are needed or point me to documentation that so defines? Thank you, Eric Kadison > -----Original Message----- > From: Liu, Yong [mailto:yong.liu@intel.com] > Sent: Saturday, September 05, 2015 5:48 PM > To: Eric Kadison; dts@dpdk.org > Subject: RE: Adding support for a new NIC on DTS >=20 > Hi Eric, > Can you show your settings in execution.cfg? By default NIC port type is = "cfg" > which mean DTS will only load ports which defined in conf/ports.cfg. >=20 > Here is one sample for port configuration file. Setting "pci" mean the pc= i > address of DUT port, "peer" mean the opposite test port pci address. > [root@dpdk-test38 dts]# cat conf/ports.cfg [DUT IP] ports=3D > pci=3D87:00.0,peer=3D07:00.0; > pci=3D87:00.1,peer=3D07:00.1; >=20 >=20 > > -----Original Message----- > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Eric Kadison > > Sent: Thursday, September 03, 2015 6:36 AM > > To: dts@dpdk.org > > Subject: [dts] Adding support for a new NIC on DTS > > > > Hi everyone, > > I'm trying to add support for a new NIC to DTS. It is clear that the > > driver needs to be identified in the settings.py file (by adding to > > the NICS dict the device name (as the key) and PCI ID (as the value), > > and then adding the kernel driver name (as value) to the same key in > > the DRIVERS dict). Did I miss anything? > > > > After entering my DUT host computer information in crbs.py, and > > setting up execution.cfg, I expected some basic tests to run. The > > hello_world test ran successfully, but it does not bind my ports to > > the igb_uio driver. So no test that tries to run I/O runs. In fact, > > it looks like the code in the project_dpdk.py file in set_target tries > > to bind the NIC to the kernel driver. Can anyone point me at a solutio= n? > > > > Test configuration use DTS from the master branch and DPDK 2.0. > > > > Eric Kadison