From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id E18935323 for ; Fri, 29 Apr 2016 20:02:21 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 29 Apr 2016 11:02:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,552,1455004800"; d="scan'208";a="965554832" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga002.jf.intel.com with ESMTP; 29 Apr 2016 11:02:13 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 29 Apr 2016 11:02:13 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.229]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.184]) with mapi id 14.03.0248.002; Sat, 30 Apr 2016 02:02:11 +0800 From: "Liu, Yong" To: "Xu, GangX" , "dts@dpdk.org" CC: "Xu, GangX" Thread-Topic: [dts] [PTCH V1 1/2] add link status interrupt test plan Thread-Index: AQHRoH+P9+DU25laR0q+MW5fOXlG1p+hQXMA Date: Fri, 29 Apr 2016 18:02:11 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14F0B0C6@SHSMSX103.ccr.corp.intel.com> References: <1461759504-30167-1-git-send-email-gangx.xu@intel.com> In-Reply-To: <1461759504-30167-1-git-send-email-gangx.xu@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjQyYmI0MTAtNDM1MS00NGJhLWExMTctZTcyZjdmMTUyMTE4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Iit0UlZ5bXFERURZdmFvNURTc1ppeTlxb2NtdU82d2g1V08xVkRMWGFjZ009In0= x-ctpclassification: CTP_IC 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] [PTCH V1 1/2] add link status interrupt test plan 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: Fri, 29 Apr 2016 18:02:22 -0000 Thanks, applied. > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,gang > Sent: Wednesday, April 27, 2016 5:18 AM > To: dts@dpdk.org > Cc: Xu, GangX > Subject: [dts] [PTCH V1 1/2] add link status interrupt test plan >=20 > Signed-off-by: xu,gang > --- > test_plans/link_status_interrupt_test_plan.rst | 65 > ++++++++++++++++++++++++++ > 1 file changed, 65 insertions(+) > create mode 100644 test_plans/link_status_interrupt_test_plan.rst >=20 > diff --git a/test_plans/link_status_interrupt_test_plan.rst > b/test_plans/link_status_interrupt_test_plan.rst > new file mode 100644 > index 0000000..60d9716 > --- /dev/null > +++ b/test_plans/link_status_interrupt_test_plan.rst > @@ -0,0 +1,65 @@ > +.. > + > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Link Status Detect > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +This tests for Detect Link Status feature can be run on linux userspace. > +It is to check if the userspace interrupt can be received after plugging > +in/out the cable/fiber on specified NIC port, and if the link status can > +be updated correctly. Futhermore, it would be better to check if packets > +can be received and sent on a specified port after its link has just up. > +So it may need layer 2 forwarding at the same time. > + > +For layer 2 forwarding, a packet received on a RX port (RX_PORT), it > would > +be transmitted from a TX port (TX_PORT=3DRX_PORT+1) if RX_PORT is even; > +otherwise from a TX port (TX_PORT=3DRX_PORT-1) if RX_PORT is odd. Before > +being transmitted, the source mac address of the packet would be replace= d > +by the mac address of the TX port, while the destination mac address > would > +be replaced by 00:09:c0:00:00:TX_PORT_ID. The test application should be > +run with the wanted paired ports configured using the coremask parameter > +via the command line. i.e. port 0 and 1 is a valid pair, while port 1 an= d > +2 isn't. The test is performed by running the test application and using > a > +traffic generator. > + > +The ``link_status_interrupt`` application is run with EAL parameters and > +parameters for the application itself. This application supports three > +parameters for itself. > + > + - ``-p PORTMASK``: hexadecimal bitmask of ports to config > + - ``-q NQ``: number of queue per lcore (default is 1) > + - ``-T PERIOD``: refresh periond in seconds (0/10/86400: > disable/default/maximum) > + > +Prerequisites > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and > enable vt-d in bios. > +When used vfio , used "modprobe vfio" and "modprobe vfio-pci" insmod > vfiod driver, then used > +"./tools/dpdk_nic_bind.py --bind=3Dvfio-pci device_bus_id" to bind vfio > driver to test driver. > +The test app need add a cmdline, "--vfio-intr=3Dint_x" > + > +Assume port 0 and 1 are connected to the remote ports, e.g. packet > generator. > +To run the test application in linuxapp environment with 4 lcores, 2 > ports and > +2 RX queues per lcore:: > + > + $ ./link_status_interrupt -c f -- -q 2 -p 0x3 > + > +Also, if the ports need to be tested are different, the port mask should > be > +changed. The lcore used to run the test application and the number of > queues > +per lcore could be changed. > + > +Test Case: Link Status Change > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > + > +Run the test application as above command. Then plug out the cable/fiber= , > or > +simulate a disconnection. After several seconds, check if the link is > actully > +off. Then plug in the cable/fiber, or simulate a connection. After > several seconds, > +check if the link is actually up, and print its information about duplex > and speed. > + > +Test Case: Port available > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > + > +Run the test application as above command with cable/fiber plugged out > from both > +port 0 and 1, then plug it in. After several seconds and the link of all > the ports > +is up. Together with packet generator, do layer 2 forwarding, and check > if the > +packets can be received on port 0/1 and sent out on port 1/0. > -- > 1.9.3