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>,
	Denis Pryazhennikov <denis.pryazhennikov@arknetworks.am>
Subject: Re: [PATCH v2] drivers: invalidate dangling MAE flow action FW resource IDs
Date: Mon, 22 May 2023 11:20:46 +0100	[thread overview]
Message-ID: <0ecaa5b3-abe8-b59a-70b2-edea53d0a44f@amd.com> (raw)
In-Reply-To: <b666e757-f775-5196-a591-d54637c001a6@oktetlabs.ru>

On 5/22/2023 7:48 AM, Andrew Rybchenko wrote:
> On 5/21/23 11:36, Ivan Malov wrote:
>> When reinserting a flow (on port restart, for instance)
>> FW resource IDs found in the action set specification
>> need to be invalidated so that the new (reallocated)
>> FW resource IDs can be accepted by libefx again.
>>
>> Fixes: 1bbd1ec2348a ("net/sfc: support action VXLAN encap in MAE
>> backend")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
>> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
>> Tested-by: Denis Pryazhennikov <denis.pryazhennikov@arknetworks.am>
> 
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> 
> 

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2023-05-22 10:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 14:30 [PATCH 1/2] common/sfc_efx/base: add API to drop MAE action " Ivan Malov
2023-04-24 14:30 ` [PATCH 2/2] net/sfc: invalidate dangling MAE flow action FW " Ivan Malov
2023-05-18 16:25 ` [PATCH 1/2] common/sfc_efx/base: add API to drop MAE action " Ferruh Yigit
2023-05-18 17:21   ` Ivan Malov
2023-05-19  8:47     ` Ferruh Yigit
2023-05-19  9:01       ` Ivan Malov
2023-05-22 10:21         ` Ferruh Yigit
2023-05-21  8:36 ` [PATCH v2] drivers: invalidate dangling MAE flow action FW " Ivan Malov
2023-05-22  6:48   ` Andrew Rybchenko
2023-05-22 10:20     ` 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=0ecaa5b3-abe8-b59a-70b2-edea53d0a44f@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=amoreton@xilinx.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=denis.pryazhennikov@arknetworks.am \
    --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).