Signed-off-by: Keith Wiles <keith.wi...@intel.com>
---
doc/guides/prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst | 10 +++++-----
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst
b/doc/guides/prog_guide/kernel_nic_interface.rst
index eb16e2e..75a359e 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -241,7 +241,7 @@ Of course, as a prerequisite, the vhost/vhost-net kernel
CONFIG should be chosen
.. code-block:: console
- examples/kni/build/app/kni -c -0xf0 -n 4 -- -p 0x3 -P
--config="(0,4,6),(1,5,7)"
+ examples/kni/build/app/kni -l 4-7 -n 4 -- -p 0x3 -P
--config="(0,4,6),(1,5,7)"
This command runs the kni sample application with two physical ports.
Each port pins two forwarding cores (ingress/egress) in user space.
diff --git a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
index 65813c9..48d88df 100644
--- a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
+++ b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
@@ -365,7 +365,7 @@ Device names and bonding options must be separated by
commas as shown below:
.. code-block:: console
- $RTE_TARGET/app/testpmd -c f -n 4 --vdev 'net_bond0,bond_opt0=..,bond
opt1=..'--vdev 'net_bond1,bond _opt0=..,bond_opt1=..'
+ $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bond0,bond_opt0=..,bond
opt1=..'--vdev 'net_bond1,bond _opt0=..,bond_opt1=..'
Link Bonding EAL Options
^^^^^^^^^^^^^^^^^^^^^^^^
@@ -465,22 +465,22 @@ Create a bonded device in round robin mode with two
slaves specified by their PC
.. code-block:: console
- $RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev 'net_bond0,mode=0,
slave=0000:00a:00.01,slave=0000:004:00.00' -- --port-topology=chained
+ $RTE_TARGET/app/testpmd -l 0-3' -n 4 --vdev 'net_bond0,mode=0,
slave=0000:00a:00.01,slave=0000:004:00.00' -- --port-topology=chained
Create a bonded device in round robin mode with two slaves specified by their
PCI address and an overriding MAC address:
.. code-block:: console
- $RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev 'net_bond0,mode=0,
slave=0000:00a:00.01,slave=0000:004:00.00,mac=00:1e:67:1d:fd:1d' --
--port-topology=chained
+ $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bond0,mode=0,
slave=0000:00a:00.01,slave=0000:004:00.00,mac=00:1e:67:1d:fd:1d' --
--port-topology=chained
Create a bonded device in active backup mode with two slaves specified, and a
primary slave specified by their PCI addresses:
.. code-block:: console
- $RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev 'net_bond0,mode=1,
slave=0000:00a:00.01,slave=0000:004:00.00,primary=0000:00a:00.01' --
--port-topology=chained
+ $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bond0,mode=1,
slave=0000:00a:00.01,slave=0000:004:00.00,primary=0000:00a:00.01' --
--port-topology=chained
Create a bonded device in balance mode with two slaves specified by their PCI
addresses, and a transmission policy of layer 3 + 4 forwarding:
.. code-block:: console
- $RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev 'net_bond0,mode=2,
slave=0000:00a:00.01,slave=0000:004:00.00,xmit_policy=l34' --
--port-topology=chained
+ $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bond0,mode=2,
slave=0000:00a:00.01,slave=0000:004:00.00,xmit_policy=l34' --
--port-topology=chained
diff --git a/doc/guides/prog_guide/multi_proc_support.rst
b/doc/guides/prog_guide/multi_proc_support.rst
index 2a996ae..9a9dca7 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -173,7 +173,7 @@ Some of these are documented below:
so it is recommended that it be disabled only when absolutely necessary,
and only when the implications of this change have been understood.
-* All DPDK processes running as a single application and using shared memory
must have distinct coremask arguments.
+* All DPDK processes running as a single application and using shared memory
must have distinct coremask/corelist arguments.
It is not possible to have a primary and secondary instance, or two
secondary instances,
using any of the same logical cores.
Attempting to do so can cause corruption of memory pool caches, among
other issues.
--
2.8.0.GIT
