test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wang, Yinan" <yinan.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>
Subject: Re: [dts] [PATCH v1] test_plans/pvp_share_lib: add pvp test plan with	share lib
Date: Wed, 29 May 2019 02:13:24 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA86509@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190521183648.40575-1-yinan.wang@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Wednesday, May 22, 2019 2:37 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v1] test_plans/pvp_share_lib: add pvp test plan with
> share lib
> 
> From: Wang Yinan <yinan.wang@intel.com>
> 
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
>  test_plans/pvp_share_lib_test_plan.rst | 84 ++++++++++++++++++++++++++
>  1 file changed, 84 insertions(+)
>  create mode 100644 test_plans/pvp_share_lib_test_plan.rst
> 
> diff --git a/test_plans/pvp_share_lib_test_plan.rst
> b/test_plans/pvp_share_lib_test_plan.rst
> new file mode 100644
> index 0000000..38f74e1
> --- /dev/null
> +++ b/test_plans/pvp_share_lib_test_plan.rst
> @@ -0,0 +1,84 @@
> +.. Copyright (c) <2019>, Intel Corporation
> +   All rights reserved.
> +
> +   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
> +   FOR 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 ANY THEORY OF LIABILITY, WHETHER IN
> CONTRACT,
> +   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> +   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> ADVISED
> +   OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +=========================================
> +Vhost/virtio-user pvp share lib test plan
> +=========================================
> +
> +Description
> +===========
> +
> +The feature need compile dpdk as shared libraries, then application should
> use option ``-d`` to load the dynamic pmd that are built as shared libraries.
> +
> +Test Case1: Vhost/virtio-user pvp share lib test with niantic
> +=============================================================
> +
> +1. Enable the shared lib in DPDK configure file::
> +
> +    vi ./config/common_base
> +    -CONFIG_RTE_BUILD_SHARED_LIB=n
> +    +CONFIG_RTE_BUILD_SHARED_LIB=y
> +
> +2. Recompile dpdk code::
> +
> +    make install T=x86_64-native-linux-gcc -j 30
> +
> +3. Export shared lib files into host environment::
> +
> +    export
> + LD_LIBRARY_PATH=/root/dpdk/x86_64-native-linuxapp-
> gcc/lib:$LD_LIBRARY_
> + PATH
> +
> +4. Bind niantic port with igb_uio, use option ``-d`` to load the dynamic pmd
> when launch vhost::
> +
> +    ./testpmd  -c 0x03 -n 4 --socket-mem 1024,1024 --legacy-mem -d
> librte_pmd_vhost.so.2.1 -d librte_pmd_ixgbe.so.2.1 -d
> librte_mempool_ring.so.1.1 \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1' -- -i
> +    testpmd>start
> +
> +5. Launch virtio-user::
> +
> +    ./testpmd -c 0x0c -n 4 --socket-mem 1024,1024 --legacy-mem -d
> librte_pmd_virtio.so.1.1 -d librte_mempool_ring.so.1.1 \
> +    --no-pci --file-prefix=virtio  --
> vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-net -- -i
> +    testpmd>start
> +
> +6. Send traffic by packet generator, check the throughput with below
> command::
> +
> +    testpmd>show port stats all
> +
> +Test Case2: Vhost/virtio-user pvp share lib test with fortville
> +===============================================================
> +
> +Similar as Test Case1, all steps are similar except step 4:
> +
> +4. Bind fortville port with igb_uio, use option ``-d`` to load the dynamic
> pmd when launch vhost::
> +
> +    ./testpmd  -c 0x03 -n 4 --socket-mem 1024,1024 --legacy-mem -d
> librte_pmd_vhost.so.2.1 -d librte_pmd_i40e.so.1.1 -d
> librte_mempool_ring.so.1.1 \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1' -- -i
> +    testpmd>start
> \ No newline at end of file
> --
> 2.17.1


      parent reply	other threads:[~2019-05-29  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 18:36 Yinan
2019-05-22  6:01 ` Li, WenjieX A
2019-05-29  2:13 ` Tu, Lijuan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8CE3E05A3F976642AAB0F4675D0AD20E0BA86509@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yinan.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).