From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 6CB923239 for ; Thu, 17 Sep 2015 02:30:57 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 16 Sep 2015 17:30:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,542,1437462000"; d="scan'208";a="806818887" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by fmsmga002.fm.intel.com with ESMTP; 16 Sep 2015 17:30:55 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 17 Sep 2015 08:30:53 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.110]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.12]) with mapi id 14.03.0248.002; Thu, 17 Sep 2015 08:30:52 +0800 From: "Liu, Yong" To: "Qiu, Michael" Thread-Topic: [dts] [PATCH] Doc: update dts parameters Thread-Index: AQHQ8JRPs8ikG/xd/USCCSBFyQhef54/3u4w Date: Thu, 17 Sep 2015 00:30:52 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EF51C4@SHSMSX103.ccr.corp.intel.com> References: <1442415709-632-1-git-send-email-yong.liu@intel.com> <52CFD54F-F882-408A-B407-0913728A1154@intel.com> In-Reply-To: <52CFD54F-F882-408A-B407-0913728A1154@intel.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="iso-2022-jp" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dts@dpdk.org" Subject: Re: [dts] [PATCH] Doc: update dts parameters 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, 17 Sep 2015 00:30:58 -0000 Michael, thanks for note that. I will send out V2 patch. > -----Original Message----- > From: Qiu, Michael > Sent: Wednesday, September 16, 2015 11:28 PM > To: Liu, Yong > Cc: dts@dpdk.org > Subject: Re: [dts] [PATCH] Doc: update dts parameters >=20 >=20 > One line may be typo error, 129.168 should be 192.168 if am I right. >=20 > Thanks, > Michael >=20 >=20 > > =1B$B:_=1B(B 2015=1B$BG/=1B(B9=1B$B7n=1B(B16=1B$BF|!$2<8a=1B(B11:02=1B$= B!$=1B(BYong Liu =1B$B > > > From: Marvin Liu > > > > Add explain for new added parameters "virttype", "debug" and "debugcase= ". > > CRB configuration file moved from python file to plain txt file. > > > > Signed-off-by: Marvin Liu > > > > diff --git a/doc/dts_gsg/conf.py b/doc/dts_gsg/conf.py > > index 9213b01..6a8c679 100644 > > --- a/doc/dts_gsg/conf.py > > +++ b/doc/dts_gsg/conf.py > > @@ -1,5 +1,5 @@ > > # BSD LICENSE > > -# Copyright(c) 2010-2014 Intel Corporation. All rights reserved. > > +# Copyright(c) 2010-2015 Intel Corporation. All rights reserved. > > # All rights reserved. > > # > > # Redistribution and use in source and binary forms, with or without > > @@ -32,7 +32,7 @@ import subprocess > > > > project =3D 'DPDK Test Suite' > > > > -copyright =3D '2014, dpdk.org' > > +copyright =3D '2015, dpdk.org' > > > > #version =3D subprocess.check_output(["make","-sRrC","../../", > "showversion"]) > > > > diff --git a/doc/dts_gsg/config.rst b/doc/dts_gsg/config.rst > > index 7276681..f5b2bc7 100644 > > --- a/doc/dts_gsg/config.rst > > +++ b/doc/dts_gsg/config.rst > > @@ -9,10 +9,11 @@ For Example, please see specific usage, you can get > these information via DPDK T > > > > .. code-block:: console > > > > - usage: main.py [-h] [--config-file CONFIG_FILE] [--git GIT] [--patc= h > PATCH] > > - [--snapshot SNAPSHOT] [--output OUTPUT] [-s] [-r] [-p > PROJECT] > > - [--suite-dir SUITE_DIR] [-t TEST_CASES [TEST_CASES ...]= ] > > - [-d DIR] > > + usage: main.py [-h] [--config-file CONFIG_FILE] [--git GIT] [-- > patch PATCH] > > + [--snapshot SNAPSHOT] [--output OUTPUT] [-s] [-r] [= - > p PROJECT] > > + [--suite-dir SUITE_DIR] [-t TEST_CASES] [-d DIR] [-= v] > > + [--virttype VIRTTYPE] [--debug] [--debugcase] > > + > > > > DPDK Test Suite supports the following parameters: > > > > @@ -23,16 +24,16 @@ DPDK Test Suite supports the following parameters: > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | -h,--help | show this help message and exit > | | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > - | --config-file CONFIG_FILE | configuration file that describes th= e > test cases, | ../execution.cfg | > > + | --config-file CONFIG_FILE | configuration file that describes th= e > test cases, | execution.cfg | > > | | DUTs and targets > | | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | --git GIT | Indicate git label to use as input > | None | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | --patch PATCH | apply a patch to the package under > test | None | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > - | --snapshot SNAPSHOT | snapshot .tgz file to use as input > | ../dpdk.tar.gz | > > + | --snapshot SNAPSHOT | snapshot .tgz file to use as input > | dep/dpdk.tar.gz | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > - | --output OUTPUT | Output directory where DPDK Test > Suite log and | ../output | > > + | --output OUTPUT | Output directory where DPDK Test > Suite log and | output | > > | | result saved > | | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | -s --skip-setup | Skips all possible setup steps done o= n > both DUT | | > > @@ -53,12 +54,21 @@ DPDK Test Suite supports the following parameters: > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | -d DIR --dir DIR | Output directory where dpdk package i= s > extracted | dpdk | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > - | --suite-dir | Test suite directory where test > suites will be | ../tests | > > + | --suite-dir | Test suite directory where test > suites will be | tests | > > | | imported > | | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > | -v, --verbose | Enable verbose output, all log shown > on screen | | > > +---------------------------+--------------------------------------= - > ------------+------------------+ > > - > > + | --virttype | Set virtualization hypervisor type. > Support kvm | | > > + | | and libvirtd by now. > | | > > + +---------------------------+-------------------------------------= - > -------------+------------------+ > > + | --debug | Enable debug mode, running process > can be | | > > + | | interrupted and enter debug mode. > | | > > + +---------------------------+-------------------------------------= - > -------------+------------------+ > > + | --debugcase | Enter into debug mode before running > every test | | > > + | | case. > | | > > + +---------------------------+-------------------------------------= - > -------------+------------------+ > > + > > Please see more information about some critical parameters as the > following: > > > > **--config-file** > > @@ -72,6 +82,7 @@ When we use ?-git parameter, DPDK Test Suite will > clone the source code from d > > **--patch** > > > > DPDK Test Suite also support apply specified patch list by --patch > parameter before build DPDK packet. > > + > > **--skip-setup** > > > > If DPDK source code doesn=1B$B!G=1B(Bt changed, you can use --skip-setu= p to skip > unzip and compilation of DPDK source code, just reuse original source cod= e. > > @@ -85,7 +96,7 @@ Parameter ?-project can load customized project model > and do its own project i > > If we perform multiple validation at the same time, result files in > output folder maybe overwritten. Then we can use ?-output parameter to > specify the output folder and save execution log and result files. This > option will make sure that all test result will be stored in the differen= t > excel files and rst files, doesn=1B$B!G=1B(Bt conflict each other. > > > > .. note:: > > - The current working folder of DPDK Test Suite is =1B$B!H=1B(Bframew= ork=1B$B!I=1B(B and > default output folder is =1B$B!H=1B(B../output=1B$B!I=1B(B > > + The current working folder of DPDK Test Suite is "DTS root > directory" and default output folder is =1B$B!H=1B(Boutput=1B$B!I=1B(B > > > > **--t** > > > > @@ -101,15 +112,39 @@ DPDK Test Suite support load suites from differen= t > folders, this will be helpful > > > > DPDK Test Suite support verbose mode. When enable this mode, all log > messages will be output on screen and helpful for debug. > > > > +**--virttype** > > + > > +Choose virtualization hypervisor type. By now this configuration is > useless. > > + > > +**--debug** > > + > > +DPDK Test Suite support debug mode. After keyboard ctrl+c message to > DTS process, will run into this mode. User can do further debug by > attached to sessions or call pdb module by interact interface. > > + > > +Debug interact support commands as below: > > + > > +.. code-block:: console > > + > > + help(): show help message > > + list(): list all connected sessions > > + connect(name): connect to session directly > > + exit(): exit dts > > + quit(): quit debug mode and into noraml mode > > + debug(): call python debug module > > + > > +**--debugcase** > > + > > +Another approach to run into debug mode. With this option on, DTS will > hang and wait for user command before execution of each test case. > > + > > DPDK Release Preparation > > ------------------------ > > > > -Firstly, you need to download the latest code from dpdk.org, then > archive and compress it in the source code folder. After that, please mov= e > this zipped file to DPDK Test Suite folder. Once launch test framework, > DPDK Test Suite will copy this zipped file to root folder on DUT. Finally > this source code zip file will be unzipped and built. > > +Firstly, you need to download the latest code from dpdk.org, then > archive and compress it into zipped file. After that, please move this > zipped file to DPDK Test Suite "dep" folder. Once launch test framework, > DPDK Test Suite will copy this zipped file to root folder on DUT. Finally > this source code zip file will be unzipped and built. > > > > .. code-block:: console > > > > - [root@tester dcts]# ls > > - [root@tester dcts]# dts dpdk.tar.gz execution.cfg framework > output test_plans tests > > + [root@tester dts]# ls > > + [root@tester dts]# conf dep doc dts executions framework output > test_plans tests tools > > + > > > > If enables patch option, DPDK Test Suite will also make patch the > unzipped folder and compile it. > > > > @@ -125,18 +160,20 @@ First of all, you must create a file named > execution.cfg as below. > > .. code-block:: console > > > > [Execution1] > > - crbs=3D10.239.128.117 > > + crbs=3D129.168.1.1 > > test_suites=3D > > hello_world, > > l2fwd > > targets=3D > > x86_64-default-linuxapp-gcc, > > parameters=3Dnic_type=3Dniantic:func=3Dtrue > > + scenario=3Dpf_passthrough > > > > * crbs: IP address of the DUT CRB. The detail information of this CRB > is defined in file crbs.py. > > * test_suites: defines list of test suites, which will plan to be > executed. > > * gets: list of DPDK targets to be tested. > > * parameters: you can define multiple keywords > > +* scenario: Senario of DPDK virtualization environment for this > execution. > > > > ? nic_type : is the type of the NIC to use. The types are defined i= n > the file settings.py. > > > > @@ -144,39 +181,44 @@ First of all, you must create a file named > execution.cfg as below. > > > > ? perf=3Dtrue run only performance test > > > > -Then please add the detail information about your CRB in **crbs.py** a= s > follows: > > +Then please add the detail information about your CRB in > **conf/crbs.conf** as follows: > > > > .. code-block:: console > > > > - crbs =3D [ > > - {'IP': '10.239.128.117', > > - 'name': 'CrownPassCRB1', > > - 'user': 'root', > > - 'pass': 'tester', > > - 'tester IP': '10.239.128.116', > > - IXIA: None, > > - 'memory channels': 4, > > - 'bypass core0': True}, > > - ] > > + [192.168.1.1] > > + dut_ip=3D192.168.1.1 > > + dut_user=3Droot > > + dut_passwd=3D > > + os=3Dlinux > > + tester_ip=3D192.168.1.2 > > + tester_passwd=3D > > + ixia_group=3Dgroup1 > > + channels=3D4 > > + bypass_core0=3DTrue > > + > > > > .. table:: > > > > +-----------------+------------------------------------------------= - > ---+ > > | Item | description > | > > +-----------------+------------------------------------------------= - > ---+ > > - | IP | IP address of DUT > | > > + | dut_ip | IP address of DUT > | > > + +-----------------+-----------------------------------------------= - > ----+ > > + | dut_user | UserName of DPDK Test Suite used to login into > DUT | > > +-----------------+------------------------------------------------= - > ---+ > > - | name | Name of DUT > | > > + | dut_passwd | Password of DPDK Test Suite used to login into > DUT | > > +-----------------+------------------------------------------------= - > ---+ > > - | user | UserName of DPDK Test Suite used to login into > DUT | > > + | os | Distribution of operation system > | > > +-----------------+------------------------------------------------= - > ---+ > > - | pass | Password of DPDK Test Suite used to login into > DUT | > > + | tester_ip | IP address of tester > | > > +-----------------+------------------------------------------------= - > ---+ > > - | Tester IP | IP address of tester > | > > + | tester_passwd | Password to login into Tester > | > > +-----------------+------------------------------------------------= - > ---+ > > - | memory channels | number of memory channels for DPDK EAL > | > > + | ixia_group | IXIA group name for this DUT > | > > +-----------------+------------------------------------------------= - > ---+ > > - | bypass core0 | skip the first core when initialize DPDK > | > > + | channels | number of memory channels for DPDK EAL > | > > + +-----------------+-----------------------------------------------= - > ----+ > > + | bypass_core0 | skip the first core when initialize DPDK > | > > +-----------------+------------------------------------------------= - > ---+ > > > > Launch DPDK Test Suite > > @@ -188,17 +230,18 @@ DPDK Test Suite will create communication session= s > first. > > > > .. code-block:: console > > > > - DUT 10.239.128.117 > > - DTS_DUT_CMD: ssh root@10.239.128.117 > > - DTS_DUT_CMD: ssh root@10.239.128.117 > > - DTS_TESTER_CMD: ssh root@10.239.128.116 > > - DCS_TESTER_CMD: ssh root@10.239.128.116 > > + DUT 192.168.1.1 > > + INFO: ssh root@192.168.1.1 > > + INFO: ssh root@192.168.1.1 > > + INFO: ssh root@192.168.1.2 > > + INFO: ssh root@192.168.1.2 > > > > > > Then copy snapshot zipped dpdk source code to DUT. > > + > > .. code-block:: console > > > > - DTS_DUT_CMD: scp ../dpdk.tar.gz root@10.239.128.117: > > + DTS_DUT_CMD: scp dep/dpdk.tar.gz root@192.168.1.1: > > > > Collect CPU core and network device information of DUT and tester. > > > > @@ -239,7 +282,7 @@ Clean-up DUT and tester after all validation > finished. > > > > .. code-block:: console > > > > - DTS_DUT_CMD: rmmod igb_uio > > + DTS_DUT_CMD: rmmod igb_uio > > DTS_DUT_CMD: modprobe igb > > DTS_DUT_CMD: modprobe ixgbe > > DTS_DUT_CMD: modprobe e1000e > > -- > > 1.9.3 > >