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 BB3B245DB9 for ; Wed, 27 Nov 2024 18:21:51 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B0C5A4066C; Wed, 27 Nov 2024 18:21:51 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 5754140A6E for ; Wed, 27 Nov 2024 18:21:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1732728109; 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=bY6ioFirMrGQzb7d5W05SIiRnL7yO0LUSMn6gT+0iok=; b=fkrP+SSRcf98HFGrZLmdWGtL2RmwpAyw6mvE++ZlDSUbPg5IgZTinLj+cp/ZklaNzDsN5w fWkxUX1+ioojpvhDIyeszsNPZQXCYjMPnEido5nhm6cbfToEkrffbt+c4oU94lFxh3JMAJ 5VqUPEWgy5ivtoa7S2m1GBOryk8pg/s= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-178-exfIunwjP_WcoAneMD3MUA-1; Wed, 27 Nov 2024 12:21:46 -0500 X-MC-Unique: exfIunwjP_WcoAneMD3MUA-1 X-Mimecast-MFC-AGG-ID: exfIunwjP_WcoAneMD3MUA Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (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-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id A38D31955EE7; Wed, 27 Nov 2024 17:21:45 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.192.52]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 023F9300019E; Wed, 27 Nov 2024 17:21:43 +0000 (UTC) From: Kevin Traynor To: Viacheslav Ovsiienko Cc: Dariusz Sosnowski , dpdk stable Subject: patch 'net/mlx5: fix number of supported flex parsers' has been queued to stable release 21.11.9 Date: Wed, 27 Nov 2024 17:18:10 +0000 Message-ID: <20241127171916.690404-63-ktraynor@redhat.com> In-Reply-To: <20241127171916.690404-1-ktraynor@redhat.com> References: <20241127171916.690404-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: fqIT_zq0mtoSVT5A5GdwMaj2nz7yDZo6AaZcFbTWxUQ_1732728105 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 21.11.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/02/24. 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/d7965234b1ade7ed3ae5f06f2af56d419ebbfe43 Thanks. Kevin --- >From d7965234b1ade7ed3ae5f06f2af56d419ebbfe43 Mon Sep 17 00:00:00 2001 From: Viacheslav Ovsiienko Date: Wed, 18 Sep 2024 16:46:19 +0300 Subject: [PATCH] net/mlx5: fix number of supported flex parsers [ upstream commit 16d8f37b4ebb59a2b2d48dbd9c0f3b8302d4ab1f ] The hardware supports up to 8 flex parser configurations. Some of them can be utilized internally by firmware, depending on the configured profile ("FLEX_PARSER_PROFILE_ENABLE" in NV-setting). The firmware does not report in capabilities how many flex parser configuration is remaining available (this is device-wide resource and can be allocated runtime by other agents - kernel, DPDK applications, etc.), and once there is no more available parsers on the parse object creation moment firmware just returns an error. Fixes: db25cadc0887 ("net/mlx5: add flex item operations") Signed-off-by: Viacheslav Ovsiienko Acked-by: Dariusz Sosnowski --- drivers/net/mlx5/mlx5.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/mlx5/mlx5.h b/drivers/net/mlx5/mlx5.h index 80c1c0b7b1..95e06916bf 100644 --- a/drivers/net/mlx5/mlx5.h +++ b/drivers/net/mlx5/mlx5.h @@ -52,5 +52,5 @@ /* Maximal number of flex items created on the port.*/ -#define MLX5_PORT_FLEX_ITEM_NUM 4 +#define MLX5_PORT_FLEX_ITEM_NUM 8 /* Maximal number of field/field parts to map into sample registers .*/ -- 2.47.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-11-27 17:17:40.244414434 +0000 +++ 0063-net-mlx5-fix-number-of-supported-flex-parsers.patch 2024-11-27 17:17:38.243269466 +0000 @@ -1 +1 @@ -From 16d8f37b4ebb59a2b2d48dbd9c0f3b8302d4ab1f Mon Sep 17 00:00:00 2001 +From d7965234b1ade7ed3ae5f06f2af56d419ebbfe43 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 16d8f37b4ebb59a2b2d48dbd9c0f3b8302d4ab1f ] + @@ -16 +17,0 @@ -Cc: stable@dpdk.org @@ -25 +26 @@ -index 5f7bfcd613..399923b443 100644 +index 80c1c0b7b1..95e06916bf 100644 @@ -28 +29 @@ -@@ -70,5 +70,5 @@ +@@ -52,5 +52,5 @@