From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@arknetworks.am>, dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
stable@dpdk.org, Andy Moreton <amoreton@xilinx.com>
Subject: Re: [PATCH 1/2] common/sfc_efx/base: allow to request MAE mark reset action
Date: Fri, 10 Mar 2023 17:20:24 +0300 [thread overview]
Message-ID: <11b4070e-f186-3a7c-a343-4e0ad57cce09@oktetlabs.ru> (raw)
In-Reply-To: <20230309042842.8709-1-ivan.malov@arknetworks.am>
On 3/9/23 07:28, Ivan Malov wrote:
> Previously, DPDK sfc driver received support for tunnel
> offload. In it, MAE needs to set intermediate mark from
> an outer rule (OR) recirculation ID in order to help
> the driver identify packets that hit the OR but miss
> on action rule (AR) lookup. But, for packets that do
> hit an AR, the driver wants to reset this mark so
> that the end receiver of traffic does not see it.
>
> The driver has a call to request such mark reset,
> but it does not work as it comes via the regular
> mark populate API, which must not be invoked
> after final delivery action has been added.
>
> Provide a suitable dedicated API for that.
>
> Fixes: 3a73dcfdb255 ("common/sfc_efx/base: match on recirc ID in action rules")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2023-03-10 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 4:28 Ivan Malov
2023-03-09 4:28 ` [PATCH 2/2] net/sfc: fix resetting mark in tunnel offload switch rules Ivan Malov
2023-03-10 14:20 ` Andrew Rybchenko
2023-03-10 14:20 ` Andrew Rybchenko [this message]
2023-03-10 15:46 ` [PATCH 1/2] common/sfc_efx/base: allow to request MAE mark reset action 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=11b4070e-f186-3a7c-a343-4e0ad57cce09@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=amoreton@xilinx.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.malov@arknetworks.am \
--cc=stable@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).