[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <391d5ef7-c8fd-4b9f-b488-23203ae96751@intel.com>
Date: Thu, 12 Sep 2024 12:10:25 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Saeed Mahameed <saeed@...nel.org>, "David S. Miller"
<davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>
CC: Saeed Mahameed <saeedm@...dia.com>, <netdev@...r.kernel.org>, Tariq Toukan
<tariqt@...dia.com>, Gal Pressman <gal@...dia.com>, Leon Romanovsky
<leonro@...dia.com>, Mark Bloch <mbloch@...dia.com>
Subject: Re: [net-next 08/15] net/mlx5: fs, add support for no append at
software level
On 9/11/2024 1:17 PM, Saeed Mahameed wrote:
> From: Mark Bloch <mbloch@...dia.com>
>
> Native capability for some steering engines lacks support for adding an
> additional match with the same value to the same flow group. To accommodate
> the NO APPEND flag in these scenarios, we include the new rule in the
> existing flow table entry (fte) without immediate hardware commitment. When
> a request is made to delete the corresponding hardware rule, we then commit
> the pending rule to hardware.
>
> Only one pending rule is supported because NO_APPEND is primarily used
> during replacement operations. In this scenario, a rule is initially added.
> When it needs replacement, the new rule is added with NO_APPEND set. Only
> after the insertion of the new rule is the original rule deleted.
>
> Signed-off-by: Mark Bloch <mbloch@...dia.com>
> Signed-off-by: Saeed Mahameed <saeedm@...dia.com>
> ---
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists