patch 'doc: update AF_XDP device plugin repository' has been queued to stable release 23.11.2
Xueming Li
xuemingl at nvidia.com
Mon Aug 12 14:49:40 CEST 2024
Hi,
FYI, your patch has been queued to stable release 23.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 08/14/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://git.dpdk.org/dpdk-stable/log/?h=23.11-staging
This queued commit can be viewed at:
https://git.dpdk.org/dpdk-stable/commit/?h=23.11-staging&id=de0c58c4b8d2eae3ed7d5ec3dfebf66589a03510
Thanks.
Xueming Li <xuemingl at nvidia.com>
---
>From de0c58c4b8d2eae3ed7d5ec3dfebf66589a03510 Mon Sep 17 00:00:00 2001
From: Maryam Tahhan <mtahhan at redhat.com>
Date: Wed, 1 May 2024 08:36:51 -0400
Subject: [PATCH] doc: update AF_XDP device plugin repository
Cc: Xueming Li <xuemingl at nvidia.com>
[ upstream commit ffcfbfc89ad27c5155858bee1a7b50a512573744 ]
Original repo is archived, there is a new active repo for plugin.
Fixup the references to the AF_XDP Device Plugin repo.
Signed-off-by: Maryam Tahhan <mtahhan at redhat.com>
Acked-by: Ciara Loftus <ciara.loftus at intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit at amd.com>
---
doc/guides/howto/af_xdp_dp.rst | 14 +++++++-------
doc/guides/nics/af_xdp.rst | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/doc/guides/howto/af_xdp_dp.rst b/doc/guides/howto/af_xdp_dp.rst
index f0f82c79f6..4ca5462c69 100644
--- a/doc/guides/howto/af_xdp_dp.rst
+++ b/doc/guides/howto/af_xdp_dp.rst
@@ -22,7 +22,7 @@ while the CNI configures and plumbs network interfaces for the Pod.
This document explains how to use the `AF_XDP Device Plugin for Kubernetes`_
with a DPDK application using the :doc:`../nics/af_xdp`.
-.. _AF_XDP Device Plugin for Kubernetes: https://github.com/intel/afxdp-plugins-for-kubernetes
+.. _AF_XDP Device Plugin for Kubernetes: https://github.com/redhat-et/afxdp-plugins-for-kubernetes
Background
@@ -80,7 +80,7 @@ then the AF_XDP PMD configures it internally.
with (older) versions of the AF_XDP DP <= commit id `38317c2`_
by explicitly setting ``dp_path`` to ``/tmp/afxdp.sock``.
-.. _38317c2: https://github.com/intel/afxdp-plugins-for-kubernetes/commit/38317c256b5c7dfb39e013a0f76010c2ded03669
+.. _38317c2: https://github.com/redhat-et/afxdp-plugins-for-kubernetes/commit/38317c256b5c7dfb39e013a0f76010c2ded03669
Prerequisites
-------------
@@ -173,7 +173,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
.. code-block:: console
- # git clone https://github.com/intel/afxdp-plugins-for-kubernetes.git
+ # git clone https://github.com/redhat-et/afxdp-plugins-for-kubernetes.git
.. note::
@@ -189,7 +189,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
* Make sure to modify the image used by the `daemonset.yml`_ file
in the deployments directory with the following configuration:
- .. _daemonset.yml : https://github.com/intel/afxdp-plugins-for-kubernetes/blob/main/deployments/daemonset.yml
+ .. _daemonset.yml : https://github.com/redhat-et/afxdp-plugins-for-kubernetes/blob/main/deployments/daemonset.yml
.. code-block:: yaml
@@ -200,7 +200,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
This will select the AF_XDP DP image that was built locally.
Detailed configuration options can be found in the AF_XDP Device Plugin `readme`_ .
- .. _readme: https://github.com/intel/afxdp-plugins-for-kubernetes#readme
+ .. _readme: https://github.com/redhat-et/afxdp-plugins-for-kubernetes#readme
* Deploy the AF_XDP Device Plugin and CNI
@@ -248,7 +248,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
For further reference please use the example provided by the AF_XDP DP `nad.yaml`_
- .. _nad.yaml: https://github.com/intel/afxdp-plugins-for-kubernetes/blob/main/examples/network-attachment-definition.yaml
+ .. _nad.yaml: https://github.com/redhat-et/afxdp-plugins-for-kubernetes/blob/main/examples/network-attachment-definition.yaml
* Run the Pod
@@ -294,7 +294,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
For further reference please see the `pod.yaml`_
- .. _pod.yaml: https://github.com/intel/afxdp-plugins-for-kubernetes/blob/main/examples/pod-spec.yaml
+ .. _pod.yaml: https://github.com/redhat-et/afxdp-plugins-for-kubernetes/blob/main/examples/pod-spec.yaml
* Run DPDK with a command like the following:
diff --git a/doc/guides/nics/af_xdp.rst b/doc/guides/nics/af_xdp.rst
index ec97d0155e..60a88c467e 100644
--- a/doc/guides/nics/af_xdp.rst
+++ b/doc/guides/nics/af_xdp.rst
@@ -157,7 +157,7 @@ use_cni
The EAL vdev argument ``use_cni`` is used to indicate that the user wishes to
enable the `AF_XDP Device Plugin for Kubernetes`_ with a DPDK application/pod.
-.. _AF_XDP Device Plugin for Kubernetes: https://github.com/intel/afxdp-plugins-for-kubernetes
+.. _AF_XDP Device Plugin for Kubernetes: https://github.com/redhat-et/afxdp-plugins-for-kubernetes
.. code-block:: console
@@ -180,7 +180,7 @@ to interact with the `AF_XDP Device Plugin for Kubernetes`_.
If this argument is not passed alongside the ``use_cni`` argument
then the AF_XDP PMD configures it internally.
-.. _AF_XDP Device Plugin for Kubernetes: https://github.com/intel/afxdp-plugins-for-kubernetes
+.. _AF_XDP Device Plugin for Kubernetes: https://github.com/redhat-et/afxdp-plugins-for-kubernetes
.. code-block:: console
--
2.34.1
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2024-08-12 20:44:05.793217338 +0800
+++ 0103-doc-update-AF_XDP-device-plugin-repository.patch 2024-08-12 20:44:02.395069353 +0800
@@ -1 +1 @@
-From ffcfbfc89ad27c5155858bee1a7b50a512573744 Mon Sep 17 00:00:00 2001
+From de0c58c4b8d2eae3ed7d5ec3dfebf66589a03510 Mon Sep 17 00:00:00 2001
@@ -4,0 +5,3 @@
+Cc: Xueming Li <xuemingl at nvidia.com>
+
+[ upstream commit ffcfbfc89ad27c5155858bee1a7b50a512573744 ]
@@ -9,2 +11,0 @@
-Cc: stable at dpdk.org
-
@@ -16,2 +17,2 @@
- doc/guides/nics/af_xdp.rst | 6 +++---
- 2 files changed, 10 insertions(+), 10 deletions(-)
+ doc/guides/nics/af_xdp.rst | 4 ++--
+ 2 files changed, 9 insertions(+), 9 deletions(-)
@@ -20 +21 @@
-index dd588c64bc..9da68e0bfa 100644
+index f0f82c79f6..4ca5462c69 100644
@@ -32 +33 @@
-@@ -90,7 +90,7 @@ then the AF_XDP PMD configures it internally to the `AF_XDP Device Plugin for Ku
+@@ -80,7 +80,7 @@ then the AF_XDP PMD configures it internally.
@@ -41 +42 @@
-@@ -183,7 +183,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
+@@ -173,7 +173,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
@@ -50 +51 @@
-@@ -199,7 +199,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
+@@ -189,7 +189,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
@@ -59 +60 @@
-@@ -210,7 +210,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
+@@ -200,7 +200,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
@@ -68 +69 @@
-@@ -258,7 +258,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
+@@ -248,7 +248,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
@@ -77 +78 @@
-@@ -304,7 +304,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
+@@ -294,7 +294,7 @@ Run dpdk-testpmd with the AF_XDP Device Plugin + CNI
@@ -87 +88 @@
-index 3da81da732..8bd17f04ae 100644
+index ec97d0155e..60a88c467e 100644
@@ -99,12 +100,3 @@
-@@ -178,7 +178,7 @@ The EAL vdev argument ``use_pinned_map`` is used to indicate that the user wishe
- load a pinned xskmap mounted by `AF_XDP Device Plugin for Kubernetes`_ in the DPDK
- application/pod.
-
--.. _AF_XDP Device Plugin for Kubernetes: https://github.com/intel/afxdp-plugins-for-kubernetes
-+.. _AF_XDP Device Plugin for Kubernetes: https://github.com/redhat-et/afxdp-plugins-for-kubernetes
-
- .. code-block:: console
-
-@@ -202,7 +202,7 @@ to explicitly tell the AF_XDP PMD where to find either:
- If this argument is not passed alongside the ``use_cni`` or ``use_pinned_map`` arguments then
- the AF_XDP PMD configures it internally to the `AF_XDP Device Plugin for Kubernetes`_.
+@@ -180,7 +180,7 @@ to interact with the `AF_XDP Device Plugin for Kubernetes`_.
+ If this argument is not passed alongside the ``use_cni`` argument
+ then the AF_XDP PMD configures it internally.
More information about the stable
mailing list