Closed labingIt closed 3 years ago
Your device does not support flow isolation. Isolated flow mode means packets not matching a flow will be discarded, or sent to the Linux kernel instead of DPDK (see https://doc.dpdk.org/guides/howto/flow_bifurcation.html). It was used mostly for verification purposes, so if we missed redirection of some packets during development, packets would be dropped instead of randomly going to any random core of a default RSS table, so we would see the drop counter increase.
Then, in the last 5 lines, we try automatically to install a redirection rules using rte_flow instead of using the global RSS table. This is because Mellanox NICs need to restart when changing the RSS table which is very slow and leads to dropping packets, but not when changing specific RSS instructions of a flow rule.
So in the end, nothing to worry about. I guess you have an Intel NIC :)
Target should be LOAD. BALANCE was an old mode used for development.
I ran the rss++ configuration demo (slightly modified dpdk.click), which gave the following output:
It can still forward packets, so I just want to make sure that it's working, right? And there is another question. It's about the TARGET argument on devicebalancer. What's the difference between load and balance? Will it affect the RSS++? Thank you in advance.