diff mbox series

doc: remove custom kernel patch link in ENA's guide

Message ID 20211123072321.1041-1-mk@semihalf.com (mailing list archive)
State Accepted, archived
Delegated to: Ferruh Yigit
Headers
Series doc: remove custom kernel patch link in ENA's guide |

Checks

Context Check Description
ci/checkpatch warning coding style issues
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/github-robot: build success github build: passed
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/iol-aarch64-unit-testing success Testing PASS
ci/iol-aarch64-compile-testing success Testing PASS
ci/iol-x86_64-unit-testing success Testing PASS
ci/iol-x86_64-compile-testing fail Testing issues

Commit Message

Michal Krawczyk Nov. 23, 2021, 7:23 a.m. UTC 
  ENAv2 device requires write combining support which isn't supported by
the upstream vfio-pci. amzn-driver repository provided non-upstream
patch to enable this feature and it was linked directly by the ENA PMD
guide.

To avoid custom kernel patch linking, the user is now guided to the AWS
ENA PMD documentation, which describes vfio-pci and ENAv2 issue more
deeply with possible workarounds on how to resolve it.

Signed-off-by: Michal Krawczyk <mk@semihalf.com>
---
 doc/guides/nics/ena.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

Comments

Ferruh Yigit Nov. 24, 2021, 10:47 a.m. UTC | #1 
On 11/23/2021 7:23 AM, Michal Krawczyk wrote:
> ENAv2 device requires write combining support which isn't supported by
> the upstream vfio-pci. amzn-driver repository provided non-upstream
> patch to enable this feature and it was linked directly by the ENA PMD
> guide.
> 
> To avoid custom kernel patch linking, the user is now guided to the AWS
> ENA PMD documentation, which describes vfio-pci and ENAv2 issue more
> deeply with possible workarounds on how to resolve it.
> 
> Signed-off-by: Michal Krawczyk <mk@semihalf.com>

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/main, thanks.
diff mbox series

Patch

diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 92b1858e7a..04fb5d4d75 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -158,9 +158,8 @@  Prerequisites
    In DPDK ``igb_uio`` it must be enabled by loading module with
    ``wc_activate=1`` flag (example below). However, mainline's vfio-pci
    driver in kernel doesn't have WC support yet (planed to be added).
-   If vfio-pci used user should be either turn off ENAv2 (to avoid performance
-   impact) or recompile vfio-pci driver with patch provided in
-   `amzn-github <https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk/enav2-vfio-patch>`_.
+   If vfio-pci is used user should follow
+   `AWS ENA PMD documentation <https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk/README.md>`_.
 
 #. Insert ``vfio-pci`` or ``igb_uio`` kernel module using the command
    ``modprobe vfio-pci`` or ``modprobe uio; insmod igb_uio.ko wc_activate=1``