patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ivan Malov <ivan.malov@arknetworks.am>,
	dev@dpdk.org
Cc: 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 15:46:54 +0000	[thread overview]
Message-ID: <eb32eee8-f8f6-6364-c972-4f3a66bd123f@amd.com> (raw)
In-Reply-To: <11b4070e-f186-3a7c-a343-4e0ad57cce09@oktetlabs.ru>

On 3/10/2023 2:20 PM, Andrew Rybchenko wrote:
> 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>
> 
> 

Series applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2023-03-10 15:47 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 ` [PATCH 1/2] common/sfc_efx/base: allow to request MAE mark reset action Andrew Rybchenko
2023-03-10 15:46   ` Ferruh Yigit [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=eb32eee8-f8f6-6364-c972-4f3a66bd123f@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=amoreton@xilinx.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --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).