From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 7D4105683 for ; Thu, 10 Sep 2015 07:57:11 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 09 Sep 2015 22:57:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,502,1437462000"; d="scan'208";a="641999922" Received: from kmsmsx151.gar.corp.intel.com ([172.21.73.86]) by orsmga003.jf.intel.com with ESMTP; 09 Sep 2015 22:57:09 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 10 Sep 2015 13:57:08 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.248]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.182]) with mapi id 14.03.0224.002; Thu, 10 Sep 2015 13:57:06 +0800 From: "Liu, Yong" To: Eric Kadison , "dts@dpdk.org" Thread-Topic: Adding support for a new NIC on DTS Thread-Index: AdDlzlubNrQFUSIUQumZM9qZnXJpfgCbjvGAALmAlSAAGeCm0A== Date: Thu, 10 Sep 2015 05:57:06 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EE5BAB@SHSMSX103.ccr.corp.intel.com> References: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com> <86228AFD5BCD8E4EBFD2B90117B5E81E10EE1BF3@SHSMSX103.ccr.corp.intel.com> <7C99D44D787C8F4B9DC7D9BF9E6680541001591E@IRVEXCHMB07.corp.ad.broadcom.com> In-Reply-To: <7C99D44D787C8F4B9DC7D9BF9E6680541001591E@IRVEXCHMB07.corp.ad.broadcom.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] 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 05:57:12 -0000 Eric, Some comments below. If need us to support on suite debug, the log file is = required to check root cause. > -----Original Message----- > From: Eric Kadison [mailto:ekadison@broadcom.com] > Sent: Thursday, September 10, 2015 12:25 PM > To: Liu, Yong; dts@dpdk.org > Subject: RE: Adding support for a new NIC on DTS >=20 > 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 >=20 > Note that: > - The DUT_PORT_MAP is built correctly. So the discovery process on the > DUT has found my NIC and discovered the correct connections to the Tester= . > The ports.cfg file has not been changed from its default. > - The NIC is bound to our PMC correctly. This is clear in the output lo= g. > At DTS completion, the kernel driver is reloaded properly. > - As you can see, I have figured out that the "drivername" argument is > required and must contain the name of the uio driver. My settings.py fil= e > contains the driver name of the kernel driver for my NIC (not the PMD). Yes, this argument is for kernel driver for the NIC. DTS also can support d= river "vfio-pci".=20 > - As you can see, I've tried the l3fwd and the jumboframes test suites. > Neither works. The helloworld test was successful. > - The l3fwd test performs setup and then runs no test cases. It appears > that DTS will only run the test cases if called out on the command line, > though I don't know why?? When I tried to add a test case function name > to the command line, it still ran nothing. Here is easy to confuse, when DTS run performance test here should be "perf= =3Dtrue". > - 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 the 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. The log files and the test_results.xls fil= e > both show the passes and failures. Here we need the log file to further check. I guess maybe packet length dif= ferent from default NIC. >=20 > A few questions: > 1. Should we expect the jumboframes test case to pass with an arbitrary > NIC with a working PMD? We do not expect every feature can work on an arbitrary NIC. If the NIC support some feature, we can add this information in conf/dpdk_t= est_case_checklist.xls. When run those suites, DTS will skip for not supported. > 2. What is needed to make the l3fwd test case execute? If there's no IXIA machine in your environment, DTS require one independent= tester CRB which will run dpdk based pktgen.=20 Driver igb_uio should also be placed at tester's root directory.=20 > 3. Can you suggest a test suite that should run without being customized > to a specific NIC? I suggest to run testpmd suite, for it only check forwarded packet. There's no special setting required in this suite. > 4. It appears that the conf directory contains a collection of > configuration files that may be needed under certain circumstances. Can > you either define when these are needed or point me to documentation that > so defines? >=20 Thanks for remind, we add few configurations for different scenarios recent= ly. There's document missing here, we will add documents soon. > Thank you, > Eric Kadison >=20 > > -----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 > > > > Hi Eric, > > Can you show your settings in execution.cfg? By default NIC port type i= s > "cfg" > > which mean DTS will only load ports which defined in conf/ports.cfg. > > > > Here is one sample for port configuration file. Setting "pci" mean the > pci > > 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; > > > > > > > -----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 trie= s > > > to bind the NIC to the kernel driver. Can anyone point me at a > solution? > > > > > > Test configuration use DTS from the master branch and DPDK 2.0. > > > > > > Eric Kadison