patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <>
To: Michael Baum <>, "" <>
Cc: Matan Azrad <>,
	Dariusz Sosnowski <>,
	 Slava Ovsiienko <>,
	Ori Kam <>, Suanming Mou <>,
	Shiri Kuzin <>,
	"" <>
Subject: RE: [PATCH] net/mlx5: fix GENEVE TLV option management
Date: Wed, 17 Jan 2024 17:14:51 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> -----Original Message-----
> From: Michael Baum <>
> Sent: Monday, January 15, 2024 2:13 PM
> To:
> Cc: Matan Azrad <>; Dariusz Sosnowski
> <>; Raslan Darawsheh <>; Slava
> Ovsiienko <>; Ori Kam <>;
> Suanming Mou <>; Shiri Kuzin <>;
> Subject: [PATCH] net/mlx5: fix GENEVE TLV option management
> In SW steering, the GENEVE TLV option matching flows must be created using
> a translation function.
> This function checks whether this option has already created a DevX object for
> the matching and either creates the objects or updates the reference counter.
> After translation, a flag in flow structure is turned on indicating the destroy
> function to release this DevX object.
> When the flow rule has meter, the rule may be split, and call translate function
> more than once per flow causing object reference counter to increase each
> time without updating the flow flag accordingly.
> This patch uses this flag as a reference counter which is increased every
> translation and indicates the destroy function how many destroy DevX to do.
> Fixes: f15f0c3806d0 ("net/mlx5: create GENEVE TLV option management")
> Fixes: e440d6cf589e ("net/mlx5: add GENEVE TLV option flow translation")
> Cc:
> Cc:
> Signed-off-by: Michael Baum <>
> Acked-by: Matan Azrad <>
Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh

      reply	other threads:[~2024-01-17 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 12:13 Michael Baum
2024-01-17 17:14 ` Raslan Darawsheh [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).