test suite reviews and discussions
 help / color / mirror / Atom feed
From: TangHaifeng <haifengx.tang@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 07/28] add unit_test_mbuf rst file into dts
Date: Tue, 26 May 2015 15:35:34 +0800	[thread overview]
Message-ID: <1432625755-19403-1-git-send-email-haifengx.tang@intel.com> (raw)

---
 test_plans/unit_tests_mbuf_test_plan.rst |   70 ++++++++++++++++++++++++++++++
 1 files changed, 70 insertions(+), 0 deletions(-)
 create mode 100644 test_plans/unit_tests_mbuf_test_plan.rst

diff --git a/test_plans/unit_tests_mbuf_test_plan.rst b/test_plans/unit_tests_mbuf_test_plan.rst
new file mode 100644
index 0000000..3b0d568
--- /dev/null
+++ b/test_plans/unit_tests_mbuf_test_plan.rst
@@ -0,0 +1,70 @@
+.. Copyright (c) <2010>, 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.
+
+==============
+Mbuf Autotests
+==============
+
+This is the test plan for the Intel® DPDK mbuf library.
+
+Description
+===========
+
+#. Allocate a mbuf pool.
+
+   - The pool contains NB_MBUF elements, where each mbuf is MBUF_SIZE
+     bytes long.
+
+#. Test multiple allocations of mbufs from this pool.
+
+   - Allocate NB_MBUF and store pointers in a table.
+   - If an allocation fails, return an error.
+   - Free all these mbufs.
+   - Repeat the same test to check that mbufs were freed correctly.
+
+#. Test data manipulation in pktmbuf.
+
+   - Alloc an mbuf.
+   - Append data using rte_pktmbuf_append().
+   - Test for error in rte_pktmbuf_append() when len is too large.
+   - Trim data at the end of mbuf using rte_pktmbuf_trim().
+   - Test for error in rte_pktmbuf_trim() when len is too large.
+   - Prepend a header using rte_pktmbuf_prepend().
+   - Test for error in rte_pktmbuf_prepend() when len is too large.
+   - Remove data at the beginning of mbuf using rte_pktmbuf_adj().
+   - Test for error in rte_pktmbuf_adj() when len is too large.
+   - Check that appended data is not corrupt.
+   - Free the mbuf.
+   - Between all these tests, check data_len and pkt_len, and
+     that the mbuf is contiguous.
+   - Repeat the test to check that allocation operations
+     reinitialize the mbuf correctly.
-- 
1.7.4.4

             reply	other threads:[~2015-05-26  7:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  7:35 TangHaifeng [this message]
2015-05-26  7:35 ` [dts] [dts 08/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 09/28] add unit_tests_pmd_perf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 10/28] add unit_test_power " TangHaifeng
2015-05-26  9:01   ` Liu, Yong
2015-05-26  7:35 ` [dts] [dts 11/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 12/28] add unit_test_ring " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 13/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 14/28] add unit_test_timer " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 15/28] add unit_test_cmdline testcase " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 16/28] add unit_test_dump " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 17/28] add unit_test_eal " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 18/28] add unit_test_ivshmem " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 19/28] add unit_test_kni " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 20/28] add unit_test_lpm " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 21/28] add unit_test_mbuf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 22/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 23/28] add unit_test_pmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 24/28] add unit_test_power " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 25/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 26/28] add unit_test_ring " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 27/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 28/28] add unit_tests_timer " TangHaifeng

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=1432625755-19403-1-git-send-email-haifengx.tang@intel.com \
    --to=haifengx.tang@intel.com \
    --cc=dts@dpdk.org \
    --cc=jingguox.fu@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).