DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] net/ice: support flow priority for DCF switch filter
Date: Fri, 16 Apr 2021 10:19:44 +0000	[thread overview]
Message-ID: <bccd8672038d465cb083410be2587d5e@intel.com> (raw)
In-Reply-To: <20210415153845.840636-1-yuying.zhang@intel.com>



> -----Original Message-----
> From: Zhang, Yuying <yuying.zhang@intel.com>
> Sent: Thursday, April 15, 2021 11:39 PM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Zhang, Yuying <yuying.zhang@intel.com>
> Subject: [PATCH v4] net/ice: support flow priority for DCF switch filter
> 
> Support rte flow priority attribute for DCF switch filter.
> When a packet is matched by two rules, the behavior of it is not defined. This
> patch supports flow priority to create different recipes for this situation. Only
> priority 0 and 1 are supported and higher value denotes higher priority.
> 
> for example:
> 1. flow create 0 priority 0 ingress pattern eth / vlan tci is 2 / vlan tci is 2 / end
> actions vf id 2 / end 2. flow create 0 priority 1 ingress pattern eth / vlan / vlan
> / ipv4 dst is 192.168.0.1 / end actions vf id 1 / end
> 
> These two rules can be created at the same time in DCF switch filter and
> priority of rule 2 is higher. Packet hits rule 2 when two conditions of rules are
> satisfied.
> 
> Signed-off-by: Yuying Zhang <yuying.zhang@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-04-16 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  7:02 [dpdk-dev] [PATCH v1] " Yuying
2021-04-12  8:54 ` [dpdk-dev] [PATCH v2] " Yuying Zhang
2021-04-15 10:58 ` [dpdk-dev] [PATCH v3] " Yuying Zhang
2021-04-15 15:38 ` [dpdk-dev] [PATCH v4] " Yuying Zhang
2021-04-16 10:19   ` Zhang, Qi Z [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=bccd8672038d465cb083410be2587d5e@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=yuying.zhang@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).