git.droids-corp.org
/
dpdk.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
examples/l3fwd: add FIB infrastructure
[dpdk.git]
/
doc
/
guides
/
sample_app_ug
/
vmdq_dcb_forwarding.rst
diff --git
a/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst
b/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst
index
83fcdf6
..
c908074
100644
(file)
--- a/
doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst
+++ b/
doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst
@@
-26,13
+26,13
@@
multiple queues. When run with 8 threads, that is, with the -c FF option, each t
As supplied, the sample application configures the VMDQ feature to have 32 pools with 4 queues each as indicated in :numref:`figure_vmdq_dcb_example`.
The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 8 queues. While the
Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDQ pools of 4 or 8 queues each. For simplicity, only 16
As supplied, the sample application configures the VMDQ feature to have 32 pools with 4 queues each as indicated in :numref:`figure_vmdq_dcb_example`.
The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 8 queues. While the
Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDQ pools of 4 or 8 queues each. For simplicity, only 16
-or 32 pools is supported in this sample. And queues numbers for each VMDQ pool can be changed by setting
CONFIG_
RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM
-in config/
common_*
file.
+or 32 pools is supported in this sample. And queues numbers for each VMDQ pool can be changed by setting RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM
+in config/
rte_config.h
file.
The nb-pools, nb-tcs and enable-rss parameters can be passed on the command line, after the EAL parameters:
.. code-block:: console
The nb-pools, nb-tcs and enable-rss parameters can be passed on the command line, after the EAL parameters:
.. code-block:: console
- ./
build/
vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss
+ ./
<build_dir>/examples/dpdk-
vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss
where, NP can be 16 or 32, TC can be 4 or 8, rss is disabled by default.
where, NP can be 16 or 32, TC can be 4 or 8, rss is disabled by default.
@@
-68,11
+68,11
@@
The application is located in the ``vmdq_dcb`` sub-directory.
Running the Application
-----------------------
Running the Application
-----------------------
-To run the example in a linux
app
environment:
+To run the example in a linux environment:
.. code-block:: console
.. code-block:: console
- user@target:~$ ./
build/
vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4
+ user@target:~$ ./
<build_dir>/examples/dpdk-
vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4
Refer to the *DPDK Getting Started Guide* for general information on running applications and
the Environment Abstraction Layer (EAL) options.
Refer to the *DPDK Getting Started Guide* for general information on running applications and
the Environment Abstraction Layer (EAL) options.
@@
-102,10
+102,6
@@
a default structure is provided for VMDQ and DCB configuration to be filled in l
.rxmode = {
.mq_mode = ETH_MQ_RX_VMDQ_DCB,
.split_hdr_size = 0,
.rxmode = {
.mq_mode = ETH_MQ_RX_VMDQ_DCB,
.split_hdr_size = 0,
- .header_split = 0, /**< Header Split disabled */
- .hw_ip_checksum = 0, /**< IP checksum offload disabled */
- .hw_vlan_filter = 0, /**< VLAN filtering disabled */
- .jumbo_frame = 0, /**< Jumbo Frame Support disabled */
},
.txmode = {
.mq_mode = ETH_MQ_TX_VMDQ_DCB,
},
.txmode = {
.mq_mode = ETH_MQ_TX_VMDQ_DCB,
@@
-169,7
+165,7
@@
the MAC of VMDQ pool 2 on port 1 is 52:54:00:12:01:02.
};
/* pool mac addr template, pool mac addr is like: 52 54 00 12 port# pool# */
};
/* pool mac addr template, pool mac addr is like: 52 54 00 12 port# pool# */
- static struct ether_addr pool_addr_template = {
+ static struct
rte_
ether_addr pool_addr_template = {
.addr_bytes = {0x52, 0x54, 0x00, 0x12, 0x00, 0x00}
};
.addr_bytes = {0x52, 0x54, 0x00, 0x12, 0x00, 0x00}
};
@@
-229,7
+225,7
@@
the MAC of VMDQ pool 2 on port 1 is 52:54:00:12:01:02.
/* Set mac for each pool.*/
for (q = 0; q < num_pools; q++) {
/* Set mac for each pool.*/
for (q = 0; q < num_pools; q++) {
- struct ether_addr mac;
+ struct
rte_
ether_addr mac;
mac = pool_addr_template;
mac.addr_bytes[4] = port;
mac.addr_bytes[5] = q;
mac = pool_addr_template;
mac.addr_bytes[4] = port;
mac.addr_bytes[5] = q;
@@
-254,7
+250,7
@@
See :doc:`l2_forward_real_virtual` for more information.
Statistics Display
~~~~~~~~~~~~~~~~~~
Statistics Display
~~~~~~~~~~~~~~~~~~
-When run in a linux
app
environment,
+When run in a linux environment,
the VMDQ and DCB Forwarding sample application can display statistics showing the number of packets read from each RX queue.
This is provided by way of a signal handler for the SIGHUP signal,
which simply prints to standard output the packet counts in grid form.
the VMDQ and DCB Forwarding sample application can display statistics showing the number of packets read from each RX queue.
This is provided by way of a signal handler for the SIGHUP signal,
which simply prints to standard output the packet counts in grid form.