From: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist: add flexible_rxd not support double vlan
Date: Fri, 24 Apr 2020 02:15:20 +0000 [thread overview]
Message-ID: <FA979DD015B0CA41A7C777E75BD0A9F003E78D49@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <20200420191858.13659-1-xiaoxiaox.zeng@intel.com>
Tested-by : Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
Best regards,
Zeng,xiaoxiao
> -----Original Message-----
> From: Zeng, XiaoxiaoX
> Sent: Tuesday, April 21, 2020 3:19 AM
> To: dts@dpdk.org
> Cc: Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
> Subject: [dts] [PATCH V1] conf/test_case_checklist: add flexible_rxd not
> support double vlan
>
> *. CVL kernel driver does`t enable double vlan which cause tester sent a
> unexpected packet.
>
> Signed-off-by: Zeng Xiaoxiao <xiaoxiaox.zeng@intel.com>
> ---
> conf/test_case_checklist.json | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 44bf8af..76811c5 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2749,5 +2749,36 @@
> "Bug ID": "",
> "Comments": "niantic not support this case"
> }
> + ],
> + "check_double_VLAN_fields_in_RXD_8021ad": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> +
> + "columbiaville_100g"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "CVL_100G kennel not support double VLAN"
> + }
> + ],
> + "check_double_VLAN_fields_in_RXD_8021Q_2_VLAN_tag": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "columbiaville_100g"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "only i40e and ixgbe driver support this case"
> + }
> ]
> }
> --
> 2.17.1
prev parent reply other threads:[~2020-04-24 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 19:18 Zeng Xiaoxiao
2020-04-21 3:32 ` Tu, Lijuan
2020-04-24 2:15 ` Zeng, XiaoxiaoX [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=FA979DD015B0CA41A7C777E75BD0A9F003E78D49@CDSMSX102.ccr.corp.intel.com \
--to=xiaoxiaox.zeng@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).