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 29478A0093 for ; Wed, 9 Mar 2022 12:02:43 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 248A640150; Wed, 9 Mar 2022 12:02:43 +0100 (CET) Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by mails.dpdk.org (Postfix) with ESMTP id E38BF410EF for ; Wed, 9 Mar 2022 12:02:41 +0100 (CET) Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) (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 smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 485E23F1C5 for ; Wed, 9 Mar 2022 11:02:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1646823761; bh=aYwT6TjPGWV5nZHDngaCh2hfdbbUcNH30UyJFL+QkE4=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=l/M2T+NnHW9aLLpq5bJ8fPF2nl7H6NRZAHp0DDuk7VevBK8JO59mT5unCQPI9ezBK SCGAcZ7DD0cgI2g3/XZyVtkcJqamftyAGYqW9iQTJaFQjLMHpwHRJQzwMG5GgQWwlJ lYE0pzZttf2xxXlPJCHCWFw1bio48d7e1emnyasvpzoK6tslSQ618JQIXjIrI/FV8w co9dZrI1vTZzhTvrowNqZoM1xjlPLnqiWN+Nf5UNvE4yG6qa2IJVl0OkPOEgfFod87 udYgwqyVcLpRZtGc6xNnWGfZOM79YSFOhOAj4KK9WKvlThx1rEwEq9rm4+7IgfIKzT jWbOfeLMSEVLw== Received: by mail-wm1-f71.google.com with SMTP id h131-20020a1c2189000000b003898de01de4so653080wmh.7 for ; Wed, 09 Mar 2022 03:02:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aYwT6TjPGWV5nZHDngaCh2hfdbbUcNH30UyJFL+QkE4=; b=sxsjRUk8B+bSnXil4lI8fqJzSHdCbtyRUhrQ4Tw4vtM7y3xbEJv2FAWjmHRr9QeqNk CIq6sJFz1KfhPzeZWxMMamsAxmD2ZQJrNTIpIN52kNnn0M7RUwp/0zd+uX8ezJql9Rli RVTsiQ6glYtBEjLD5WcKRT+zTKiIkVXF1v415bcQkKnCmmgtJPicxoW1mQXUz9WRxb5M F1dAZC2FVo8N/z/E9WBgwiKzB0TVlDcTw1N6boniv5l0wE/u2M7VCv9D3llD1VD7mfOF EO/mAgVu1mECyMmNqM8mdA96GWpd2yXOE9SmX+ScAuzuqITMZFaIpBB/rITEY+JWwlwP rEQQ== X-Gm-Message-State: AOAM5300HSiSd/obvxxP3ce1q0QI26xiaiYxgScqtir+eeTU0ncuB3Kn ko9A6Fuu2cbwkGCODMycv5XyvncAaADwBZWx1lhSUfNN8ye0FqgLxHMWqgCrl16aU6GEta7Dahn XDB5/7IcVD/OJ4PVMnH0gLAMj X-Received: by 2002:adf:ef81:0:b0:1f0:95f:30a7 with SMTP id d1-20020adfef81000000b001f0095f30a7mr15250018wro.636.1646823760941; Wed, 09 Mar 2022 03:02:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJyDr4xG47l04MKRMnzFCIsz6toxmiw6iqGfXnR9QIdt3aQtp2G8AexPli7drabVvvVhsl9THQ== X-Received: by 2002:adf:ef81:0:b0:1f0:95f:30a7 with SMTP id d1-20020adfef81000000b001f0095f30a7mr15249994wro.636.1646823760619; Wed, 09 Mar 2022 03:02:40 -0800 (PST) Received: from localhost.localdomain (068-133-067-156.ip-addr.inexio.net. [156.67.133.68]) by smtp.gmail.com with ESMTPSA id a8-20020a05600c068800b00389bdc8c8c2sm1361092wmn.12.2022.03.09.03.02.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Mar 2022 03:02:39 -0800 (PST) From: christian.ehrhardt@canonical.com To: Michael Baum Cc: Raslan Darawsheh , Viacheslav Ovsiienko , dpdk stable Subject: patch 'doc: remove obsolete vector Tx explanations from mlx5 guide' has been queued to stable release 19.11.12 Date: Wed, 9 Mar 2022 12:00:54 +0100 Message-Id: <20220309110116.1295395-23-christian.ehrhardt@canonical.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220309110116.1295395-1-christian.ehrhardt@canonical.com> References: <20220309110116.1295395-1-christian.ehrhardt@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 19.11.12 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 03/11/22. 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/cpaelzer/dpdk-stable-queue This queued commit can be viewed at: https://github.com/cpaelzer/dpdk-stable-queue/commit/9d74f3ab284eea3338476a12348574b46df8d369 Thanks. Christian Ehrhardt --- >From 9d74f3ab284eea3338476a12348574b46df8d369 Mon Sep 17 00:00:00 2001 From: Michael Baum Date: Wed, 23 Feb 2022 15:48:30 +0200 Subject: [PATCH] doc: remove obsolete vector Tx explanations from mlx5 guide [ upstream commit 9c7dc70265696ef402ed6f54a2552ed7684560aa ] Vectorized routines were removed in result of Tx datapath refactoring, and devarg keys documentation was updated. However, more updating should have been done. In environment variables doc, there was explanation according to vectorized Tx which isn't relevant anymore. This patch removes this irrelevant explanation. Fixes: a6bd4911ad93 ("net/mlx5: remove Tx implementation") Signed-off-by: Michael Baum Reviewed-by: Raslan Darawsheh Acked-by: Viacheslav Ovsiienko --- doc/guides/nics/mlx5.rst | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index 6deea36537..8a1b4f82b1 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -325,15 +325,6 @@ Environment variables The register would be flushed to HW usually when the write-combining buffer becomes full, but it depends on CPU design. - Except for vectorized Tx burst routines, a write memory barrier is enforced - after updating the register so that the update can be immediately visible to - HW. - - When vectorized Tx burst is called, the barrier is set only if the burst size - is not aligned to MLX5_VPMD_TX_MAX_BURST. However, setting this environmental - variable will bring better latency even though the maximum throughput can - slightly decline. - Run-time configuration ~~~~~~~~~~~~~~~~~~~~~~ -- 2.35.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2022-03-09 11:57:44.576144072 +0100 +++ 0023-doc-remove-obsolete-vector-Tx-explanations-from-mlx5.patch 2022-03-09 11:57:43.372938256 +0100 @@ -1 +1 @@ -From 9c7dc70265696ef402ed6f54a2552ed7684560aa Mon Sep 17 00:00:00 2001 +From 9d74f3ab284eea3338476a12348574b46df8d369 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 9c7dc70265696ef402ed6f54a2552ed7684560aa ] + @@ -16 +17,0 @@ -Cc: stable@dpdk.org @@ -26 +27 @@ -index c3cc0c0f41..3f5c8bb303 100644 +index 6deea36537..8a1b4f82b1 100644 @@ -29 +30 @@ -@@ -557,15 +557,6 @@ Environment variables +@@ -325,15 +325,6 @@ Environment variables