From: Lijuan Tu <lijuan.tu@intel.com>
To: changqingxwu <changqingx.wu@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH V2] test_plans/external_memory_test_plan_V2
Date: Thu, 27 Dec 2018 01:21:27 +0800 [thread overview]
Message-ID: <2590bf11-65b7-ac4f-e1f7-2afd2f7c3fc9@intel.com> (raw)
In-Reply-To: <1545804525-102300-1-git-send-email-changqingx.wu@intel.com>
Applied, thanks
On 2018年12月26日 14:08, changqingxwu wrote:
> add new external_memory_test_plan_V2
>
> Signed-off-by: changqingxwu <changqingx.wu@intel.com>
> ---
> test_plans/external_memory_test_plan.rst | 93 ++++++++++++++++++++++++
> 1 file changed, 93 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..42f5772
> --- /dev/null
> +++ b/test_plans/external_memory_test_plan.rst
> @@ -0,0 +1,93 @@
> +.. Copyright (c) <2015-2018>, 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.
> +
> +=========================================
> +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 case 1: IGB_UIO and anonymous memory allocation
> +-----------------------------------------------------
> +Bind the ports to IGB_UIO driver
> +
> +Start testpmd with --mp-alloc=xmem flag::
> +
> + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmem -i
> +
> +Start forward in testpmd
> +
> +Start send traffic from outside to test the forward function
> +
> +
> +Test case 2: IGB_UIO and anonymous hugepage memory allocation
> +--------------------------------------------------------------
> +
> +Bind the ports to IGB_UIO driver
> +
> +Start testpmd with --mp-alloc=xmemhuge flag::
> +
> + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmemhuge -i
> +
> +Start forward in testpmd
> +
> +Start send traffic from outside to test the forward function
> +
> +
> +Test case 3: VFIO and anonymous memory allocation
> +--------------------------------------------------
> +Bind the ports to vfio-pci driver
> +
> +Start testpmd with --mp-alloc=xmem flag::
> +
> + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmem -i
> +
> +Start forward in testpmd
> +
> +Start send traffic from outside to test the forward function
> +
> +
> +Test case 4: VFIO and anonymous hugepage memory allocation
> +-----------------------------------------------------------
> +Bind the ports to vfio-pci driver
> +
> +Start testpmd with --mp-alloc=xmemhuge flag::
> +
> + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- --mp-alloc=xmemhuge -i
> +
> +Start forward in testpmd
> +
> +Start send traffic from outside to test the forward function
> \ No newline at end of file
prev parent reply other threads:[~2018-12-26 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 6:08 changqingxwu
2018-12-26 6:46 ` Zhu, ShuaiX
2018-12-26 17:21 ` Lijuan Tu [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=2590bf11-65b7-ac4f-e1f7-2afd2f7c3fc9@intel.com \
--to=lijuan.tu@intel.com \
--cc=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).