Merge "Updated release info" into developEnea_NFV_Access_2.2.3_RC8Enea_NFV_Access_2.2.3_RC7dummy-ap656-outdated

2 files changed, 21 insertions, 17 deletions

diff --git a/.gitreview b/.gitreview
index 30e070b..ef53a12 100644
--- a/.gitreview
+++ b/.gitreview
@@ -1,5 +1,5 @@
 [gerrit]
 host=gerrit.enea.se
 port=29418
-project=linux/el_releases-nfv-access
-defaultbranch=rocko
+project=linux/nfv-access-documentation
+defaultbranch=develop
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index 0980783..ec2c584 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -120,22 +120,26 @@
       within same security domain (e.g. host system or VNF). Therefore it is
       not possible to bind only some of them to the
       <literal>vfio-pci</literal> driver, while the rest are managed by other
-      drivers. In this case the <literal>igb_uio</literal> driver will be used
+      drivers. In this case the <literal>igb_uio</literal> driver shall be used
       instead for the entire IOMMU group.</para>
 
-      <para>If UEFI Secure Boot is enabled, the Linux kernel disallows the use
-      of the UIO framework, therefore network devices intended for use by DPDK
-      must be bound to the <literal>vfio-pci</literal> driver rather than the
-      <literal>igb_uio</literal>. However, the limitation stated above still
-      applies so all the interfaces must be assigned to
-      <literal>vfio-pci</literal>.</para>
-
-      <para>When an in-band management bridge is configured with DPDK enabled,
-      the <literal>igb_uio</literal> driver is used. If the in-band management
-      interface is assigned to a VM, and there are other interfaces assigned
-      to the VM that use the <literal>vfio-pci</literal> driver (this includes
-      SR-IOV interfaces and PCI passthrough interfaces), then the VM must be
-      stopped before restarting the vCPE service on the device
+      <para>Driver selection for DPDK-assigned interfaces is a system-wide
+      configuration, therefore selecting <literal>igb_uio</literal>
+      or <literal>vfio-pci</literal> when adding a DPDK interface will not
+      influence the actual driver used. In this release, NFV Access runtime
+      software is using <literal>vfio-pci</literal> driver by default, but
+      <literal>igb_uio</literal> can be used instead by providing custom
+      scripting. Please contact Enea for further details.</para>
+      <para>Using both <literal>igb_uio</literal> driver for DPDK interfaces
+      and <literal>vfio-pci</literal> for SR-IOV/PCI-Passthrough is possible,
+      but not recomended, as it might not be supported by some hardware
+      configurations.</para>
+
+      <para>When an in-band management bridge uses the
+      <literal>igb_uio</literal> driver and the VM connected to the bridge has
+      other interfaces that use the <literal>vfio-pci</literal> driver (e.g.
+      SR-IOV/PCI-Passthrough), then the VM must be stopped before restarting
+      the vCPE service on the device
       (<command>systemctl restart vcpe</command>). Rebooting the device does
       not have this restriction.</para>
     </listitem>
@@ -170,4 +174,4 @@
 
   <!-- <xi:include href="jiraissues_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
\ No newline at end of file
+</chapter>