DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, dev@dpdk.org
Cc: orika@nvidia.com, matan@nvidia.com, thomas@monjalon.net
Subject: Re: [PATCH v4] ethdev: add flow rule actions update API
Date: Wed, 24 May 2023 12:00:10 +0100	[thread overview]
Message-ID: <946695f5-9872-eaaf-93d4-c5728df91918@amd.com> (raw)
In-Reply-To: <20230523183948.3403023-1-akozyrev@nvidia.com>

On 5/23/2023 7:39 PM, Alexander Kozyrev wrote:
> Introduce the new rte_flow_actions_update() API allowing users
> to update the action list in the already existing rule.
> Flow rules can be updated now without the need to destroy
> the rule first and create a new one instead.
> A single API call ensures that no packets are lost by
> guaranteeing atomicity and flow state correctness.
> The rte_flow_async_actions_update() is added as well.
> The matcher is not updated, only the action list is.
> 
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
>

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


      reply	other threads:[~2023-05-24 11:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 19:58 [PATCH] " Alexander Kozyrev
2023-05-18 15:37 ` Ori Kam
2023-05-18 19:54   ` Alexander Kozyrev
2023-05-18 19:49 ` [PATCH v2] " Alexander Kozyrev
2023-05-18 21:48   ` [PATCH v3] " Alexander Kozyrev
2023-05-21 19:07     ` Ori Kam
2023-05-22 10:28     ` Ferruh Yigit
2023-05-23  6:59       ` Ori Kam
2023-05-23 10:34         ` Ferruh Yigit
2023-05-23 11:20           ` Ori Kam
2023-05-23 18:39     ` [PATCH v4] " Alexander Kozyrev
2023-05-24 11:00       ` 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=946695f5-9872-eaaf-93d4-c5728df91918@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.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).