X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fnics%2Fnfp.rst;h=309fa5d39de138fd9134b5e16c922a27a2f66625;hb=4d6e0352e137a11972f40c18687be8135489a02e;hp=927c03c63baf9c23bef4e4e3560467a134360d08;hpb=b2a99605bc3c00b85a42afd8ce5690f5539a70f8;p=dpdk.git

diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 927c03c63b..309fa5d39d 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -75,7 +75,7 @@ compile it along with other DPDK PMDs even if no BSP was installed previously.
 Of course, a DPDK app will require such a BSP installed for using the
 NFP PMD, along with a specific NFP firmware application.
 
-Default PMD configuration is at the **common_linuxapp configuration** file:
+Default PMD configuration is at the **common_linux configuration** file:
 
 - **CONFIG_RTE_LIBRTE_NFP_PMD=y**
 
@@ -145,6 +145,18 @@ is no support for RX interrupts and it is not possible either to use those PF
 ports with the device hotplug functionality.
 
 
+PF multiprocess support
+-----------------------
+
+Due to how the driver needs to access the NFP through a CPP interface, which implies
+to use specific registers inside the chip, the number of secondary processes with PF
+ports is limited to only one.
+
+This limitation will be solved in future versions but having basic multiprocess support
+is important for allowing development and debugging through the PF using a secondary
+process which will create a CPP bridge for user space tools accessing the NFP.
+
+
 System configuration
 --------------------