test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yinan <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Wang Yinan <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans: add test plan for dpdk hugetlbfs mount size test
Date: Thu, 27 Jun 2019 19:50:13 +0000	[thread overview]
Message-ID: <20190627195013.94256-1-yinan.wang@intel.com> (raw)

From: Wang Yinan <yinan.wang@intel.com>

Signed-off-by: Wang Yinan <yinan.wang@intel.com>
---
 .../dpdk_hugetlbfs_mount_size_test_plan.rst   | 129 ++++++++++++++++++
 1 file changed, 129 insertions(+)
 create mode 100644 test_plans/dpdk_hugetlbfs_mount_size_test_plan.rst

diff --git a/test_plans/dpdk_hugetlbfs_mount_size_test_plan.rst b/test_plans/dpdk_hugetlbfs_mount_size_test_plan.rst
new file mode 100644
index 0000000..6d0eb88
--- /dev/null
+++ b/test_plans/dpdk_hugetlbfs_mount_size_test_plan.rst
@@ -0,0 +1,129 @@
+.. Copyright (c) <2016>, 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 Hugetlbfs Mount Size Feature Test Plan
+===========================================
+
+This feature is to limit DPDK to use the exact size which is the mounted hugepage size.
+
+Prerequisites
+=============
+
+To test this feature, following options need to pass the the kernel:
+hugepagesz=1G hugepages=8 default_hugepagesz=1G
+
+Test Case 1: default hugepage size w/ and w/o numa
+==================================================
+
+1. Create and mount hugepages::
+
+    mount -t hugetlbfs hugetlbfs /mnt/huge
+
+2. Bind one nic port to igb_uio driver, launch testpmd::
+
+    ./testpmd -c 0x3 -n 4 --huge-dir /mnt/huge --file-prefix=abc -- -i
+    testpmd>start
+
+3. Send packet with packet generator, check testpmd could forward packets correctly.
+
+4. Goto step 2 resart testpmd with numa support::
+
+    ./testpmd -c 0x3 -n 4 --huge-dir /mnt/huge --file-prefix=abc -- -i --numa
+    testpmd>start
+
+5. Send packets with packet generator, make sure testpmd could receive and fwd packets correctly.
+
+Test Case 2: mount size exactly match total hugepage size with two mount points
+===============================================================================
+
+1. Create and mount hugepages::
+
+    mount -t hugetlbfs -o size=4G hugetlbfs /mnt/huge1
+    mount -t hugetlbfs -o size=4G hugetlbfs /mnt/huge2
+
+2. Bind two nic ports to igb_uio driver, launch testpmd with numactl::
+
+    numactl --membind=1 ./testpmd -l 31-32 -n 4 --legacy-mem --socket-mem 0,2048 --huge-dir /mnt/huge1 --file-prefix=abc -w 82:00.0 -- -i --socket-num=1 --no-numa
+    testpmd>start
+
+    numactl --membind=1 ./testpmd -l 33-34 -n 4 --legacy-mem --socket-mem 0,2048  --huge-dir /mnt/huge2 --file-prefix=bcd -w 82:00.1 -- -i --socket-num=1 --no-numa
+    testpmd>start
+
+3. Send packets with packet generator, make sure two testpmd could receive and fwd packets correctly.
+
+Test Case 3: mount size greater than total hugepage size with single mount point
+================================================================================
+
+1. Create and mount hugepage::
+
+    mount -t hugetlbfs -o size=9G hugetlbfs /mnt/huge
+
+2. Bind one nic port to igb_uio driver, launch testpmd::
+
+    ./testpmd -c 0x3 -n 4 --legacy-mem --huge-dir /mnt/huge --file-prefix=abc -- -i
+    testpmd>start
+
+3. Send packets with packet generator, make sure testpmd could receive and fwd packets correctly.
+
+Test Case 4: mount size greater than total hugepage size with multiple mount points
+===================================================================================
+
+1. Create and mount hugepage::
+
+    mount -t hugetlbfs -o size=4G hugetlbfs /mnt/huge1
+    mount -t hugetlbfs -o size=4G hugetlbfs /mnt/huge2
+    mount -t hugetlbfs -o size=1G hugetlbfs /mnt/huge3
+
+2. Bind one nic port to igb_uio driver, launch testpmd::
+
+    numactl --membind=0 ./testpmd -c 0x3 -n 4  --legacy-mem --socket-mem 2048,0 --huge-dir /mnt/huge1 --file-prefix=abc -- -i --socket-num=0 --no-numa
+    testpmd>start
+
+    numactl --membind=0 ./testpmd -c 0xc -n 4  --legacy-mem --socket-mem 2048,0 --huge-dir /mnt/huge2 --file-prefix=bcd -- -i --socket-num=0 --no-numa
+    testpmd>start
+
+    numactl --membind=0 ./testpmd -c 0x30 -n 4  --legacy-mem --socket-mem 1024,0 --huge-dir /mnt/huge3 --file-prefix=fgh -- -i --socket-num=0 --no-numa
+    testpmd>start
+
+3. Send packets with packet generator, check first and second testpmd will start correctly while third one will report error with not enough mem in socket 0.
+
+Test Case 5: run dpdk app in limited hugepages controlled by cgroup
+===================================================================
+
+1. Bind one nic port to igb_uio driver, launch testpmd in limited hugepages::
+
+    cgcreate -g hugetlb:/test-subgroup
+    cgset -r hugetlb.1GB.limit_in_bytes=2147483648 test-subgroup
+    cgexec -g hugetlb:test-subgroup numactl -m 1 ./testpmd -c 0x3000 -n 4 -- -i --socket-num=1 --no-numa
+
+2. Start testpmd and send packets with packet generator, make sure testpmd could receive and fwd packets correctly.
-- 
2.17.1


             reply	other threads:[~2019-06-28  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 19:50 Yinan [this message]
2019-07-10  6:17 ` Tu, Lijuan

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=20190627195013.94256-1-yinan.wang@intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    /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).