test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	"Chen@dpdk.org" <Chen@dpdk.org>
Subject: Re: [dts] [PATCH V1] Add ABI stable test cases
Date: Tue, 3 Mar 2020 05:24:08 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBE8E10@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200217074311.190784-1-zhaoyan.chen@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Chen, Zhaoyan
> Sent: Monday, February 17, 2020 3:43 PM
> To: dts@dpdk.org
> Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>; Chen@dpdk.org
> Subject: [dts] [PATCH V1] Add ABI stable test cases
> 
>  Define compiling steps and common test steps.
>  Reuse exisiting test suites to cover ABI stable checking.
> 
> Signed-off-by: Chen, Zhaoyan <zhaoyan.chen@intel.com>
> 
> ---
>  test_plans/ABI_stable_test.rst | 150 +++++++++++++++++++++++++++++++++
>  1 file changed, 150 insertions(+)
>  create mode 100644 test_plans/ABI_stable_test.rst
> 
> diff --git a/test_plans/ABI_stable_test.rst b/test_plans/ABI_stable_test.rst
> new file mode 100644 index 0000000..bc8deb4
> --- /dev/null
> +++ b/test_plans/ABI_stable_test.rst
> @@ -0,0 +1,150 @@
> +.. Copyright (c) <2019-2020>, 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.
> +
> +=====================
> +DPDK ABI Stable Tests
> +=====================
> +
> +Description
> +===========
> +
> +This test suite includes both functional and performance test cases to
> +ensure that DPDK point releases (xx.02, xx.05, xx.08) are not only
> +binary compatible, but are also functionally and reasonably performance
> +compatibly with the previous vxx.11 release.
> +
> +
> +Compiling Steps
> +===============
> +
> +Compile shared library/application from DPDK xx.11 release.
> +Change the option in config/common_base configuration file::
> +
> +  CONFIG_RTE_BUILD_SHARED_LIB=y
> +
> +And then, compile the DPDK::
> +
> +  make install -j T=x86_64-native-linuxapp-gcc
> +
> +Keep this DPDK folder as <dpdk_xx11>, e.g. <dpdk_1911>.
> +
> +Compile shared library from DPDK point releasees (xx.02, xx.05, xx.08).
> +Command lines are same to above.
> +Keep this DPDK folder as <dpdk_xxxx>. e.g. <dpdk_2002>
> +
> +Setup library path in environment::
> +
> +  export LD_LIBRARY_PATH=$LD_LIBRARY_PATH,<dpdk_2002>
> +
> +
> +Common Test Steps
> +=================
> +
> +Comparing to test static dpdk application, ABI stable checking use
> +dynamic dpdk application, and shared library. Launching dynamic dpdk
> +application steps are below,
> +
> +Go into <dpdk_1911> directory, launch application with specific library::
> +
> +  testpmd -c 0xf -n 4 -d <dpdk_2002> -- -i
> +
> +Expect the application could launch successfully.
> +
> +Then, execute test steps with the application.
> +
> +Reuse our existing test suites for ABI stable checking.
> +
> +
> +Execute Test Suites
> +===================
> +
> +  +===============================+========================+
> +  |       Test Suites              |          Type           |
> +  +===============================+========================+
> +  |   unit_tests_cmdline           |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_crc               |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_dump              |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_eal               |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_kni               |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_loopback          |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_lpm               |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_mbuf              |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_mempool           |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_pmd_perf          |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_power             |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_qos               |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_ringpmd           |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_ring              |     functional          |
> +  +-------------------------------+------------------------+
> +  |   unit_tests_timer             |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_1024_ethports          |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_dequeue_zero_copy      |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_enqueue_interrupt      |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_event_idx_interrupt    |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_multi_queue_qemu       |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_pmd_xstats             |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_virtio_user_interrupt  |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_user_live_migration    |     functional          |
> +  +-------------------------------+------------------------+
> +  |   flow_classify                |     functional          |
> +  +-------------------------------+------------------------+
> +  |   flow_classify_softnic        |     functional          |
> +  +-------------------------------+------------------------+
> +  |   vhost_virtio_pmd_interrupt   |     functional          |
> +  +-------------------------------+------------------------+
> +  |   l2fwd                        |     performance         |
> +  +-------------------------------+------------------------+
> +  |   nic_single_core_perf         |     performance         |
> +  +-------------------------------+------------------------+
> +  |   l3fwd                        |     performance         |
> +  +-------------------------------+------------------------+
> --
> 2.22.0


  reply	other threads:[~2020-03-03  5:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  7:43 Chen, Zhaoyan
2020-03-03  5:24 ` Tu, Lijuan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-17  7:41 Chen, Zhaoyan

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=8CE3E05A3F976642AAB0F4675D0AD20E0BBE8E10@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=Chen@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=zhaoyan.chen@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).