From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_supportlist:add suppport Nic on CVL.
Date: Mon, 16 Dec 2019 03:09:32 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BB380A7@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1576462601-72719-1-git-send-email-shuaix.zhu@intel.com>
Hi, shuai
As all the cases in suite flexible_rxd only support CVL, and you have judge the nic in suite's set_up_all, so I think you do not need add additional checklist.
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
Sent: Monday, December 16, 2019 10:17 AM
To: dts@dpdk.org
Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>; Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V1] conf/test_case_supportlist:add suppport Nic on CVL.
The case only supports cvl Nic:
check_single_VLAN_fields_in_RXD_8021Q,
check_single_VLAN_fields_in_RXD_8021ad,
check_double_VLAN_fields_in_RXD_8021Q_1_VLAN_tag,
check_double_VLAN_fields_in_RXD_8021Q_2_VLAN_tag,
check_double_VLAN_fields_in_RXD_8021ad,
check_IPv4_fields_in_RXD,
check_IPv6_fields_in_RXD,
check_IPv6_flow_field_in_RXD,
check_TCP_fields_in_IPv4_in_RXD,
check_TCP_fields_in_IPv6_in_RXD,
check_IPv4_IPv6_TCP_fields_in_RXD_on_specific_queues
Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
---
conf/test_case_supportlist.json | 176 ++++++++++++++++++++++++++++++++
1 file changed, 176 insertions(+)
diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json index ffb2e6b..3857a53 100644
--- a/conf/test_case_supportlist.json
+++ b/conf/test_case_supportlist.json
@@ -1717,5 +1717,181 @@
"Bug ID": "",
"Comments": "This case currently support for niantic"
}
+ ],
+ "check_single_VLAN_fields_in_RXD_8021Q": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_single_VLAN_fields_in_RXD_8021ad": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_double_VLAN_fields_in_RXD_8021Q_1_VLAN_tag": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_double_VLAN_fields_in_RXD_8021Q_2_VLAN_tag": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_double_VLAN_fields_in_RXD_8021ad": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_IPv4_fields_in_RXD": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_IPv6_fields_in_RXD": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_IPv6_flow_field_in_RXD": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_TCP_fields_in_IPv4_in_RXD": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_TCP_fields_in_IPv6_in_RXD": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
+ ],
+ "check_IPv4_IPv6_TCP_fields_in_RXD_on_specific_queues": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_25g",
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "this case only support on CVL"
+ }
]
}
--
2.17.2
prev parent reply other threads:[~2019-12-16 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 2:16 zhu,shuai
2019-12-16 3:09 ` Ma, LihongX [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=BE1E572D0441E34284F1F8B7AC28F1970BB380A7@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.zhu@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).