From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7F40346211 for ; Thu, 13 Feb 2025 11:02:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7AB4142EE7; Thu, 13 Feb 2025 11:02:37 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 7346442EE7 for ; Thu, 13 Feb 2025 11:02:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1739440956; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=s9EfAjaGCbCKUhLfyrPnldS/UT/oYgsCaJZDsqn9v5c=; b=XxiiOlH95wpAB/+9zVKF8mwTjR8+XhAqFrrtTNQXHy1hghhtOGv30qS4mh8KOZ8MVF64QD PWRw2eKaBF+aflhejI1wOSGo06h2ogVXzq0bwT1ig4VIebym+Y5d0h43qfwZrc2g3X0g5+ MRMZ5r/ySg27VI9nFBzoq5NY85kSlrw= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-29-xTgHosUaPwGF2Fq85XXqag-1; Thu, 13 Feb 2025 05:02:30 -0500 X-MC-Unique: xTgHosUaPwGF2Fq85XXqag-1 X-Mimecast-MFC-AGG-ID: xTgHosUaPwGF2Fq85XXqag_1739440950 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id ED7F2180087A; Thu, 13 Feb 2025 10:02:29 +0000 (UTC) Received: from rh.Home (unknown [10.45.224.21]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 7876F1800365; Thu, 13 Feb 2025 10:02:28 +0000 (UTC) From: Kevin Traynor To: Maayan Kashani Cc: Dariusz Sosnowski , dpdk stable Subject: patch 'net/mlx5: adjust actions per rule limitation' has been queued to stable release 24.11.2 Date: Thu, 13 Feb 2025 09:58:39 +0000 Message-ID: <20250213095933.362078-72-ktraynor@redhat.com> In-Reply-To: <20250213095933.362078-1-ktraynor@redhat.com> References: <20250213095933.362078-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: QrWlJAqMJHL-szRmDoKCLW6uyMPuplZouV3jEZRvme8_1739440950 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 24.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 02/17/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/5879ea0136df2220babafd0d9a601f3aeb82795f Thanks. Kevin --- >From 5879ea0136df2220babafd0d9a601f3aeb82795f Mon Sep 17 00:00:00 2001 From: Maayan Kashani Date: Tue, 28 Jan 2025 09:54:03 +0200 Subject: [PATCH] net/mlx5: adjust actions per rule limitation [ upstream commit ab54e17fe2f5207d7b988d568344570e156551ad ] HWS implementation added a limitation of 16 actions per rule, which was incompatible with SWS limitation of 32 actions per rule. Changing the hard coded limitation in PMD to 32. Fixes: f13fab23922b ("net/mlx5: add flow jump action") Signed-off-by: Maayan Kashani Acked-by: Dariusz Sosnowski --- drivers/net/mlx5/mlx5_flow.h | 2 +- drivers/net/mlx5/mlx5_flow_hw.c | 3 --- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/net/mlx5/mlx5_flow.h b/drivers/net/mlx5/mlx5_flow.h index 757bbf73c1..9c8892b194 100644 --- a/drivers/net/mlx5/mlx5_flow.h +++ b/drivers/net/mlx5/mlx5_flow.h @@ -1584,5 +1584,5 @@ struct mlx5_hw_modify_header_action { /* The maximum actions support in the flow. */ -#define MLX5_HW_MAX_ACTS 16 +#define MLX5_HW_MAX_ACTS 32 /* DR action set struct. */ diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c index 2b62711413..501bf33f94 100644 --- a/drivers/net/mlx5/mlx5_flow_hw.c +++ b/drivers/net/mlx5/mlx5_flow_hw.c @@ -22,7 +22,4 @@ static struct rte_flow_fp_ops mlx5_flow_hw_fp_ops; -/* The maximum actions support in the flow. */ -#define MLX5_HW_MAX_ACTS 16 - /* * The default ipool threshold value indicates which per_core_cache -- 2.48.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-02-12 17:29:42.196083323 +0000 +++ 0072-net-mlx5-adjust-actions-per-rule-limitation.patch 2025-02-12 17:29:34.451946532 +0000 @@ -1 +1 @@ -From ab54e17fe2f5207d7b988d568344570e156551ad Mon Sep 17 00:00:00 2001 +From 5879ea0136df2220babafd0d9a601f3aeb82795f Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit ab54e17fe2f5207d7b988d568344570e156551ad ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -22 +23 @@ -index 93c2406abc..445c9cdb4b 100644 +index 757bbf73c1..9c8892b194 100644