test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH] test_plans: Add unit_tests_loopback_test_plan
Date: Fri, 19 Oct 2018 07:21:36 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B97BE6E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1538037925-16542-1-git-send-email-yuan.peng@intel.com>

Comments inline

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Yuan
> Sent: Thursday, September 27, 2018 4:45 PM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>
> Subject: [dts] [PATCH] test_plans: Add unit_tests_loopback_test_plan
> 
> Add unit_tests_loopback_test_plan.rst to test_plans
> 
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
> 
> diff --git a/test_plans/unit_tests_loopback_test_plan.rst
> b/test_plans/unit_tests_loopback_test_plan.rst
> new file mode 100644
> index 0000000..fe5498d
> --- /dev/null
> +++ b/test_plans/unit_tests_loopback_test_plan.rst
> @@ -0,0 +1,86 @@
> +.. Copyright (c) <2014-2017>, 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.
> +
> +====================================
> +Unit Tests: single port MAC loopback
> +====================================
> +
> +According to loopback mode, setup loopback link or not.
> +If loopback mode is setted, packets will be sent to rx_q from tx_q directly.
> +Else if loopback mode is disabled, packets will sent to peer port from tx_q.
> +Loopback mode can be used to support testing task.
> +
> +
> +Prerequisites
> +=============
> +
> +Two 40Gb Ethernet ports of the DUT are directly connected and link is up.
[Lijuan] I think it support more NICs, Could you clarify the topology?
> +
> +
> +single port MAC loopback
> +========================
> +
> +This is the test plan for unit test to verify if XL710 can enable
> +single port mac loopback.
> +
> +1. enable loopback mode:
> +In dpdk/test/test/test_pmd_perf.c
> +set::
> +
> +    .lpbk_mode=1
> +    #define MAX_TRAFFIC_BURST              32
> +
> +then make test
> +start test::
> +
> +    ./test/test/test -c f -n 4 -- -i
> +    RTE>>pmd_perf_autotest
> +
> +The final output of the test will be matrix of average cycles of IO
> +used per packet, and "Test OK" is printed out.
> +the peer port can't receive any packet.
> +
> +2. disable lookback mode:
> +In dpdk/test/test/test_pmd_perf.c
> +set::
> +
> +    .lpbk_mode=0
> +    #define MAX_TRAFFIC_BURST              32
> +
> +then make test
> +start test::
> +
> +    ./test/test/test -c f -n 4 -- -i
> +    RTE>>pmd_perf_autotest
> +
> +there is not "Test OK" presented.
> +the peer port can receive all the 32 packets.
> --
> 2.5.0

      reply	other threads:[~2018-10-19  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  8:45 Peng Yuan
2018-10-19  7:21 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0B97BE6E@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yuan.peng@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).