From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] conf/checklist:fortpark not support flowctrl_pause_fwd_on
Date: Mon, 12 Aug 2019 06:40:01 +0000 [thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B5377292A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1565624046-48199-1-git-send-email-wenjiex.a.li@intel.com>
Tested-by: Li, WenjieX A <wenjiex.a.li@intel.com>
> -----Original Message-----
> From: Li, WenjieX A
> Sent: Monday, August 12, 2019 11:34 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts][PATCH V1] conf/checklist:fortpark not support
> flowctrl_pause_fwd_on
>
> If set pasue, the packet type error when use kernel driver send packet with i40e
> nics. Add fortpark_TLV in checklist.
> 1. link_flowctrl/flowctrl_off_pause_fwd_on
> 2. link_flowctrl/flowctrl_on_pause_fwd_on
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> conf/test_case_checklist.json | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index
> 913039b..65efec0 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -400,7 +400,8 @@
> "fortville_eagle",
> "fortville_spirit",
> "fortville_spirit_single",
> - "fortville_25g"
> + "fortville_25g",
> + "fortpark_TLV"
> ],
> "Target": [
> "ALL"
> @@ -435,7 +436,8 @@
> "fortville_eagle",
> "fortville_spirit",
> "fortville_spirit_single",
> - "fortville_25g"
> + "fortville_25g",
> + "fortpark_TLV"
> ],
> "Target": [
> "ALL"
> --
> 2.17.1
prev parent reply other threads:[~2019-08-12 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 15:34 Wenjie Li
2019-08-12 6:40 ` Li, WenjieX A [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=8688172CD5C0B74590FAE19D9579F94B5377292A@SHSMSX103.ccr.corp.intel.com \
--to=wenjiex.a.li@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).