Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| en:dpi:load_balancer:setting [2025/12/22 15:39] – [Setting /etc/dpi/fastdpi.conf] elena.krasnobryzh | en:dpi:load_balancer:setting [2025/12/23 07:38] (current) – [Setting /etc/dpi/fastdpi.conf] elena.krasnobryzh |
|---|
| * ''1'' — read/write engine with two dispatcher threads: a dispatcher for each direction; | * ''1'' — read/write engine with two dispatcher threads: a dispatcher for each direction; |
| * ''2'' — Read/write engine with RSS support: for each direction, ''dpdk_rss'' dispatchers are created (default ''dpdk_rss=2''), so total number of dispatchers = 2 * ''dpdk_rss''— to work with in_dev, and a separate dispatcher to work with out_dev.\\ When the parameter value is 2, the ''mqrx_lb_engine'' engine is activated. The principle of operation is the same as in the usual mode ''dpdk_engine=2'', only rss is enabled on in_dev, and only one rx queue is created on out_dev.\\ \\ Learn more about the ''dpdk_engine'' parameter by [[en:dpi:dpi_components:platform:dpi_config#the_dispatcher_thread_load|clicking here]]. | * ''2'' — Read/write engine with RSS support: for each direction, ''dpdk_rss'' dispatchers are created (default ''dpdk_rss=2''), so total number of dispatchers = 2 * ''dpdk_rss''— to work with in_dev, and a separate dispatcher to work with out_dev.\\ When the parameter value is 2, the ''mqrx_lb_engine'' engine is activated. The principle of operation is the same as in the usual mode ''dpdk_engine=2'', only rss is enabled on in_dev, and only one rx queue is created on out_dev.\\ \\ Learn more about the ''dpdk_engine'' parameter by [[en:dpi:dpi_components:platform:dpi_config#the_dispatcher_thread_load|clicking here]]. |
| - Set the parameter ''lb_hash_type'' to ''0'' to use the ''maglev'' traffic balancing algorithm (algorithm with a fixed-size hash table). The hash for balancing is calculated as follows: | - The ''lb_hash_type'' parameter is used to select the hashing algorithm. Currently, the maglev algorithm is supported (parameter value ''0'') — an algorithm with a fixed-size hash table. The hash for load balancing is calculated as follows: |
| * if both src and dst IPs are local, the hash is calculated based on these two addresses; | * if both src and dst IPs are local, the hash is calculated based on these two addresses; |
| * if only the src IP is local, the hash is calculated based on the src IP; | * if only the src IP is local, the hash is calculated based on the src IP; |
