From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 8A91B47D0 for ; Fri, 29 Apr 2016 20:09:00 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga104.fm.intel.com with ESMTP; 29 Apr 2016 11:09:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,552,1455004800"; d="scan'208";a="965559062" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga002.jf.intel.com with ESMTP; 29 Apr 2016 11:09:01 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 29 Apr 2016 11:08:59 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX155.amr.corp.intel.com (10.18.116.71) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 29 Apr 2016 11:08:58 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.229]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.45]) with mapi id 14.03.0248.002; Sat, 30 Apr 2016 02:08:57 +0800 From: "Liu, Yong" To: "Xu, GangX" , "dts@dpdk.org" CC: "Xu, GangX" Thread-Topic: [dts] [PATCH V1 1/2] add netmap test plan Thread-Index: AQHRoez5UTy61HUXTkq4v9QPxmGOGZ+hP61w Date: Fri, 29 Apr 2016 18:08:56 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14F0B149@SHSMSX103.ccr.corp.intel.com> References: <1461916423-32178-1-git-send-email-gangx.xu@intel.com> In-Reply-To: <1461916423-32178-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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWFlZGJmNGQtZTZkMS00NGMzLTk4OGEtMzY2ZjlmNzk0MGExIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Im1KdWFtbVRYazJOa2oyWlVTYXBZZVZpY2dxUnZta3lrK0YzRm5wRUlmZjA9In0= 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] [PATCH V1 1/2] add netmap 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:09:01 -0000 Gang, few comments below. > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,gang > Sent: Friday, April 29, 2016 12:54 AM > To: dts@dpdk.org > Cc: Xu, GangX > Subject: [dts] [PATCH V1 1/2] add netmap test plan >=20 > Signed-off-by: xu,gang > --- > test_plans/netmap_compat_test_plan.rst | 125 > +++++++++++++++++++++++++++++++++ > 1 file changed, 125 insertions(+) > create mode 100644 test_plans/netmap_compat_test_plan.rst >=20 > diff --git a/test_plans/netmap_compat_test_plan.rst > b/test_plans/netmap_compat_test_plan.rst > new file mode 100644 > index 0000000..96f2a2b > --- /dev/null > +++ b/test_plans/netmap_compat_test_plan.rst > @@ -0,0 +1,125 @@ > +.. BSD LICENSE > + Copyright(c) 2010-2014 Intel Corporation. All rights reserved. > + All rights reserved. Please update the copyright time period, it should be 2010-2016. > + > + Redistribution and use in source and binary forms, with or without > + modification, are permitted provided that the following conditions > + are met: > + > + * Redistributions of source code must retain the above copyright > + notice, this list of conditions and the following disclaimer. > + * Redistributions in binary form must reproduce the above copyright > + notice, this list of conditions and the following disclaimer in > + the documentation and/or other materials provided with the > + distribution. > + * Neither the name of Intel Corporation nor the names of its > + contributors may be used to endorse or promote products derived > + from this software without specific prior written permission. > + > + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS > + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT > + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FO= R > + A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT > + OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL= , > + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT > + LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE= , > + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON AN= Y > + THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT > + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE US= E > + OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > + > + > +Netmap Compatibility Sample Application > +=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +Introduction > +------------ > + > +The Netmap compatibility library provides a minimal set of APIs to give > programs written against the Netmap APIs > +the ability to be run, with minimal changes to their source code, using > the DPDK to perform the actual packet I/O. > + > +Since Netmap applications use regular system calls, like ``open()``, > ``ioctl()`` and > +``mmap()`` to communicate with the Netmap kernel module performing the > packet I/O, > +the ``compat_netmap`` library provides a set of similar APIs to use in > place of those system calls, > +effectively turning a Netmap application into a DPDK application. > + > +The provided library is currently minimal and doesn't support all the > features that Netmap supports, > +but is enough to run simple applications, such as the bridge example > detailed below. > + > +Knowledge of Netmap is required to understand the rest of this section. > +Please refer to the Netmap distribution for details about Netmap. > + > + > +Compiling the "bridge" Sample Application > +----------------------------------------- > + > +#. Go to the example directory: > + > + .. code-block:: console > + > + export RTE_SDK=3D/path/to/rte_sdk > + cd ${RTE_SDK}/examples/netmap_compat > + > +#. Set the target (a default target is used if not specified). For > example: > + > + .. code-block:: console > + > + export RTE_TARGET=3Dx86_64-native-linuxapp-gcc > + > + See the *DPDK Getting Started Guide for Linux* for possible > ``RTE_TARGET`` values. > + > +#. Build the application: > + > + .. code-block:: console > + > + make > + Just plain text is enough, please remove rst format indicator.=20 > +Running the "bridge" Sample Application > +--------------------------------------- > + > +The application requires a single command line option: > + > +.. code-block:: console > + > + ./build/bridge [EAL options] -- -i INTERFACE_A [-i INTERFACE_B] > + > +where, > + > +* ``-i INTERFACE``: Interface (DPDK port number) to use. > + > + If a single ``-i`` parameter is given, the interface will send back > all the traffic it receives. > + If two ``-i`` parameters are given, the two interfaces form a bridge= , > + where traffic received on one interface is replicated and sent to th= e > other interface. > + > +For example, to run the application in a linuxapp environment using port > 0 and 2: > + > +.. code-block:: console > + > + ./build/bridge [EAL options] -- -i 0 -i 2 > + > +Refer to the *DPDK Getting Started Guide for Linux* for general > information on running applications and > +the Environment Abstraction Layer (EAL) options. > + > +Test Case1: netmap compat with one port > +=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Run bridge with one port:: > + ./examples/netmap_compat/build/bridge -c 0x1e -n 4 -- -i 0 > +waked up : > + Port 0 now in Netmap mode > + Bridge up and running! > + > +Send one packet on Port0,check this port receive packet. > +It receive one packet that it send. > + > +Test Case2: netmap compat with two port > +=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Run bridge with one port:: > + ./examples/netmap_compat/build/bridge -c 0x1e -n 4 -- -i 0 -i 1 > +waked up : > + Port 0 now in Netmap mode > + Port 1 now in Netmap mode > + Bridge up and running! > + > +Send one packet on Port0,check the port1 receive packet. > +It receive one packet that the port0 send. > + > -- > 1.9.3