diff options
Diffstat (limited to 'docs/vpp/configuration/dataplane/interface.rst')
| -rw-r--r-- | docs/vpp/configuration/dataplane/interface.rst | 33 |
1 files changed, 18 insertions, 15 deletions
diff --git a/docs/vpp/configuration/dataplane/interface.rst b/docs/vpp/configuration/dataplane/interface.rst index ce9a28ec..28778da9 100644 --- a/docs/vpp/configuration/dataplane/interface.rst +++ b/docs/vpp/configuration/dataplane/interface.rst @@ -20,21 +20,6 @@ Interfaces connected to the VPP dataplane use the DPDK driver by default, provid Some network interface cards (NICs) may not be compatible with the DPDK driver. -.. _vpp_config_dataplane_interface_rx_mode: - -rx-mode -------- - -The rx-mode parameter defines how VPP handles incoming packets on the interface. There are several modes available, each with its own advantages and use cases: - -- ``interrupt``: In this mode, VPP relies on hardware interrupts to notify it of incoming packets. This mode is suitable for low to moderate traffic loads and can help reduce CPU usage during idle periods. It is not recommended if low-latency processing is required. May not be supported by some NICs. -- ``polling``: In polling mode, VPP continuously checks the interface for incoming packets. This mode is ideal for high-throughput scenarios where low latency is critical, as it minimizes the time packets spend waiting to be processed. However, it can lead to higher CPU usage, especially during periods of low traffic, because the polling process is always active. -- ``adaptive``: Adaptive mode combines the benefits of both interrupt and polling modes. VPP starts in interrupt mode and switches to polling mode when the traffic load increases. - -.. cfgcmd:: set vpp settings interface <interface-name> rx-mode <mode> - -The choice of rx-mode should be based on the expected traffic patterns and performance requirements of the network environment. - dpdk-options ------------ @@ -53,6 +38,24 @@ DPDK options you can configure are: - ``num-tx-desc``: Defines the size of each transmit queue. Larger sizes can help manage bursts of outgoing traffic more effectively. - ``promisc``: Enables or disables promiscuous mode on the interface. When promiscuous mode is enabled, the interface will receive all packets on the network, regardless of type and destination of the packets. Some NICs need this feature to be enabled to avoid filtering out packets (for example to pass VLAN tagged packets). +Global Interface Parameters +=========================== + +.. _vpp_config_dataplane_interface_rx_mode: + +interface-rx-mode +----------------- + +The interface-rx-mode parameter defines how VPP handles incoming packets on interfaces. There are several modes available, each with its own advantages and use cases: + +- ``interrupt``: In this mode, VPP relies on hardware interrupts to notify it of incoming packets. This mode is suitable for low to moderate traffic loads and can help reduce CPU usage during idle periods. It is not recommended if low-latency processing is required. May not be supported by some NICs. +- ``polling``: In polling mode, VPP continuously checks the interface for incoming packets. This mode is ideal for high-throughput scenarios where low latency is critical, as it minimizes the time packets spend waiting to be processed. However, it can lead to higher CPU usage, especially during periods of low traffic, because the polling process is always active. +- ``adaptive``: Adaptive mode combines the benefits of both interrupt and polling modes. VPP starts in interrupt mode and switches to polling mode when the traffic load increases. + +.. cfgcmd:: set vpp settings interface-rx-mode <mode> + +The choice of rx-mode should be based on the expected traffic patterns and performance requirements of the network environment. + Potential Issues and Troubleshooting ==================================== |