From: lijuan.tu@intel.com
To: dts@dpdk.org,Zhimin Huang <zhiminx.huang@intel.com>
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts][PATCH V1 2/2] tests/ice_fdir:add mark id to adapt fdir rule
Date: 28 Jun 2022 18:41:17 -0700 [thread overview]
Message-ID: <f10ab6$hneu7m@fmsmga007-auth.fm.intel.com> (raw)
In-Reply-To: <20220623111538.25162-2-zhiminx.huang@intel.com>
On Thu, 23 Jun 2022 19:15:38 +0800, Zhimin Huang <zhiminx.huang@intel.com> wrote:
> according to dpdk e4a0a7599d974f05665fec3e4c251659f0b11453.
> the switch has higher prirority than fdir,for rules that support both switch and fdir
> will take into switch.
> so we need add mark id to ensure take rules into fdir.
>
> Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-06-29 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 11:15 [dts][PATCH V1 1/2] test_plans/ice_fdir:add " Zhimin Huang
2022-06-23 11:15 ` [dts][PATCH V1 2/2] tests/ice_fdir:add " Zhimin Huang
2022-06-29 1:41 ` lijuan.tu [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='f10ab6$hneu7m@fmsmga007-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=zhiminx.huang@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).