From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Dekel Peled <dekelp@mellanox.com>, <orika@mellanox.com>,
<john.mcnamara@intel.com>, <marko.kovacevic@intel.com>,
<thomas@monjalon.net>, <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: refine ethernet and VLAN flow rule items
Date: Sun, 3 May 2020 12:56:19 +0300 [thread overview]
Message-ID: <b35b1716-cbd7-a85b-1a95-8b0498b5e35d@solarflare.com> (raw)
In-Reply-To: <c42d881f0696c3a363b9a214bb4c2439271bf323.1588489972.git.dekelp@mellanox.com>
On 5/3/20 10:17 AM, Dekel Peled wrote:
> Specified pattern may be translated in different manner.
> For example the pattern "eth / ipv4" can be translated to match
> untagged packets only, since the pattern doesn't specify a VLAN item.
> It can also be translated to match both tagged and untagged packets,
> for the same reason.
> This patch updates the rte_flow documentation to clearly specify the
> required pattern to use.
> For example:
> To match tagged ipv4 packets, the pattern "eth / vlan / ipv4 / end"
> should be used.
> To match untagged ipv4 packets, the pattern "eth / ipv4 / end"
> should be used.
> To match all IPV4 packets, both tagged and untagged, need to apply
> two rules with the patterns above.
> To match both tagged and untagged packets of any type, the pattern
> "eth / end" should be used.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2020-05-03 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 18:30 [dpdk-dev] [PATCH] " Dekel Peled
2020-04-25 14:00 ` Andrew Rybchenko
2020-04-26 9:18 ` Dekel Peled
2020-04-26 17:02 ` Stephen Hemminger
2020-04-27 6:52 ` Ori Kam
2020-05-03 7:17 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2020-05-03 9:56 ` Andrew Rybchenko [this message]
2020-05-03 14:57 ` Ori Kam
2020-05-07 14:18 ` Ferruh Yigit
2020-05-05 16:51 ` Ferruh Yigit
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=b35b1716-cbd7-a85b-1a95-8b0498b5e35d@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=asafp@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=orika@mellanox.com \
--cc=thomas@monjalon.net \
/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).