From: "Wu,ChangqingX" <changqingx.wu@intel.com>
To: dts@dpdk.org
Cc: "Wu,ChangqingX" <changqingx.wu@intel.com>
Subject: [dts] [PATCH V1] test_plans/add_new_feature_externel_memory
Date: Thu, 20 Dec 2018 11:02:02 +0800 [thread overview]
Message-ID: <1545274922-35545-1-git-send-email-changqingx.wu@intel.com> (raw)
add_new_feature_externel_memory
Signed-off-by: Wu,ChangqingX <changqingx.wu@intel.com>
---
test_plans/external_memory_test_plan.rst | 43 ++++++++++++++++++++++++
1 file changed, 43 insertions(+)
create mode 100644 test_plans/external_memory_test_plan.rst
diff --git a/test_plans/external_memory_test_plan.rst b/test_plans/external_memory_test_plan.rst
new file mode 100644
index 0000000..23fec9b
--- /dev/null
+++ b/test_plans/external_memory_test_plan.rst
@@ -0,0 +1,43 @@
+Ability to use external memory test plan
+=========================================
+
+Description:
+------------
+Provide an abstraction for DPDK hugepage allocation, to have a "default" memory
+allocator that will allocate hugepages, but also have custom allocator support for
+external memory.
+
+Test cases:
+-----------
+
+Test case 1: IGB_UIO and anonymous memory allocation
+steps:
+1. bind the ports to IGB_UIO driver;
+2. start testpmd with --mp-alloc=xmem flag:
+# ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmem -i
+3. start forward in testpmd;
+4. start send traffic from outside to test the forward function;
+
+Test case 2: IGB_UIO and anonymous hugepage memory allocation
+steps:
+1. bind the ports to IGB_UIO driver;
+2. start testpmd with --mp-alloc=xmemhuge flag:
+# ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmemhuge -i
+3. start forward in testpmd;
+4. start send traffic from outside to test the forward function;
+
+Test case 3: VFIO and anonymous memory allocation
+steps:
+1. bind the ports to vfio-pci driver;
+2. start testpmd with --mp-alloc=xmem flag:
+# ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmem -i
+3. start forward in testpmd;
+4. start send traffic from outside to test the forward function;
+
+Test case 4: VFIO and anonymous hugepage memory allocation
+steps:
+1. bind the ports to vfio-pci driver;
+2. start testpmd with --mp-alloc=xmemhuge flag:
+# ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmemhuge -i
+3. start forward in testpmd;
+4. start send traffic from outside to test the forward function;
--
2.17.2
next reply other threads:[~2018-12-20 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 3:02 Wu,ChangqingX [this message]
2018-12-21 2:05 ` Zhu, ShuaiX
2018-12-22 2:24 ` 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=1545274922-35545-1-git-send-email-changqingx.wu@intel.com \
--to=changqingx.wu@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).