From: yongjie <yongjiex.gu@intel.com>
To: dts@dpdk.org
Cc: Gu yongjie <yongjiex.gu@intel.com>
Subject: [dts] [PATCH] add coremask test plan
Date: Thu, 22 Oct 2015 15:26:14 +0800 [thread overview]
Message-ID: <1445498775-12590-1-git-send-email-yongjiex.gu@intel.com> (raw)
From: Gu yongjie <yongjiex.gu@intel.com>
Signed-off-by: Gu yongjie <yongjiex.gu@intel.com>
---
test_plans/coremask_test_plan.rst | 89 +++++++++++++++++++++++++++++++++++++
1 files changed, 89 insertions(+), 0 deletions(-)
create mode 100644 test_plans/coremask_test_plan.rst
diff --git a/test_plans/coremask_test_plan.rst b/test_plans/coremask_test_plan.rst
new file mode 100644
index 0000000..0570221
--- /dev/null
+++ b/test_plans/coremask_test_plan.rst
@@ -0,0 +1,89 @@
+.. 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.
+
+Prerequisites
+=============
+
+This test will run in any machine able to run ``test``. No traffic will be sent.
+No extra needs for ports.
+
+
+Test Case: individual coremask
+==============================
+
+Launch ``test`` once per core, set the core mask for the core::
+
+ ./x86_64-default-linuxapp-gcc/app/test -c <One core mask> -n 4
+
+
+Verify: every time the application is launched the core is properly detected
+and used.
+
+Stop ``test``.
+
+
+Test Case: big coremask
+=======================
+
+Launch ``test`` with a mask bigger than the available cores::
+
+ ./x86_64-default-linuxapp-gcc/app/test -c <128 bits mask> -n 4
+
+
+Verify: the application handles the mask properly and all the available cores
+are detected and used.
+
+Stop ``test``.
+
+Test Case: all cores
+====================
+
+Launch ``test`` with all the available cores::
+
+ ./x86_64-default-linuxapp-gcc/app/test -c <All cores mask> -n 4
+
+
+Verify: all the cores have been detected and used by the application.
+
+Stop ``test``.
+
+Test Case: wrong coremask
+=========================
+
+Launch ``test`` with several wrong masks::
+
+ ./x86_64-default-linuxapp-gcc/app/test -c <Wrong mask> -n 4
+
+
+Verify: the application complains about the mask and does not start.
+
+Stop ``test``.
--
1.7.4.4
next reply other threads:[~2015-10-22 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 7:26 yongjie [this message]
2015-10-22 7:26 ` [dts] [PATCH] add testsuite coremask yongjie
-- strict thread matches above, loose matches on Subject: below --
2015-10-14 2:09 [dts] [PATCH] add coremask test plan yongjie
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=1445498775-12590-1-git-send-email-yongjiex.gu@intel.com \
--to=yongjiex.gu@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).