From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH 05/12] add link bonding rss dynamic config test plane
Date: Thu, 11 May 2017 15:37:40 +0800 [thread overview]
Message-ID: <1494488267-42592-6-git-send-email-huilongx.xu@intel.com> (raw)
In-Reply-To: <1494488267-42592-1-git-send-email-huilongx.xu@intel.com>
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
| 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
--git a/test_plans/pmdrss_hash_test_plan.rst b/test_plans/pmdrss_hash_test_plan.rst
index 4922d3b..eda7103 100644
--- a/test_plans/pmdrss_hash_test_plan.rst
+++ b/test_plans/pmdrss_hash_test_plan.rst
@@ -149,4 +149,23 @@ Test Case: test_simple_symmetric
The same as the above two test cases. Just pay attention to set the hash function to "simple xor"
+Test Case: test_dynamic_rss_bond_config
+=================================
+This case test bond slaves will auto sync rss hash config, so it only support fortville nic.
+#1. set up testpmd woth fortville NICs::
+./testpmd -c f -n 4 -- -i --portmask 0x3 --txqflags=0
+#2 creat bond device with mode 3::
+ create bonded device 3 0
+#3 add slave to bond device::
+ add bonding slave 0 2
+ add bonding slave 1 2
+#4 get default hash algorithm on slave::
+ get_hash_global_config 0
+ get_hash_global_config 1
+#5 set hash algorithm on slave 0::
+ set_hash_global_config 0 simple_xor ipv4-other enable
+#6 get hash algorithm on slave 0 and 1::
+ get_hash_global_config 0
+ get_hash_global_config 1
+#7 check slave 0 and 1 use same hash algorithm
--
1.9.3
next prev parent reply other threads:[~2017-05-11 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 7:37 [dts] [PATCH 00/12] sync inntel dts and dts org xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 01/12] fix check packet failure by lldp have different packet size xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 02/12] remove --disable-crc-strip parameter in testpmd xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 03/12] update fdir test case xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 04/12] update fdir test plane xu,huilong
2017-05-11 7:37 ` xu,huilong [this message]
2017-05-11 7:37 ` [dts] [PATCH 06/12] add dynamic rss bond config case xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 07/12] update testpmd path in dpdk xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 08/12] fix timeout when setup dpdk app xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 09/12] add filter lldp in sniff model xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 10/12] add fortville 25G NIC for this case xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 11/12] fix compile error xu,huilong
2017-05-11 7:37 ` [dts] [PATCH 12/12] fix eeporm file check xu,huilong
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=1494488267-42592-6-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).