From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 1/5] test_plans/cvl_iavf_ip_fragment_rte_flow:modify testplan to adapt dpdk changed
Date: Mon, 1 Nov 2021 05:04:11 +0000 [thread overview]
Message-ID: <BN0PR11MB5712538700C1C8E26C87FB46FD8A9@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211101120056.12228-1-zhiminx.huang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
> -----Original Message-----
> From: Huang, ZhiminX <zhiminx.huang@intel.com>
> Sent: Monday, November 1, 2021 8:01 PM
> To: dts@dpdk.org
> Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
> Subject: [dts] [PATCH V1 1/5] test_plans/cvl_iavf_ip_fragment_rte_flow:modify
> testplan to adapt dpdk changed
>
> 1.according to 54d78462344e2b3ec0a54cb6f13af0bf3da47032.
> the default rss not support ipfrag rss, need take a rss rule to enable ipfrag rss
> for fdir test.
>
> 2.according to e4a0a7599d974f05665fec3e4c251659f0b11453.
> switch have high priority,should take the rule with mark into fdir.
>
> Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
> ---
Tested-by: Zhimin Huang <zhiminx.huang@intel.com >
[-- Attachment #2: TestCvlIpFragmentRteFlow.log --]
[-- Type: application/octet-stream, Size: 411194 bytes --]
[-- Attachment #3: TestCvlIavfIpFragmentRteFlow.log --]
[-- Type: application/octet-stream, Size: 343701 bytes --]
next prev parent reply other threads:[~2021-11-01 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 12:00 Zhimin Huang
2021-11-01 5:04 ` Huang, ZhiminX [this message]
2021-11-01 12:00 ` [dts] [PATCH V1 2/5] test_plans/cvl_ip_fragment_rte_flow:modify " Zhimin Huang
2021-11-01 12:00 ` [dts] [PATCH V1 3/5] tests/cvl_iavf_ip_fragment_rte_flow:modify testcase " Zhimin Huang
2021-11-01 12:00 ` [dts] [PATCH V1 4/5] tests/cvl_ip_fragment_rte_flow:modify " Zhimin Huang
2021-11-01 12:00 ` [dts] [PATCH V1 5/5] tests/rte_flow_common:modify flow common " Zhimin Huang
2021-11-05 13:28 ` Tu, Lijuan
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=BN0PR11MB5712538700C1C8E26C87FB46FD8A9@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@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).