4 Commits (3f7a50eeb721bcc2a9f14b4d62925d46e5f202c6)

Author	SHA1	Message	Date
Lukas Sismis	3f7a50eeb7	dpdk/ixgbe: setup RSS for Intel IXGBE PMD ... Set RSS hash function according to Intel IXGBE PMD available hash functions. During configuration, a warning appeared stating that RSS hash function has been changed from one value to the other. This has meant that the supported hash functions did not cover all required hash functions by the configuration. This commit solves the warning.	4 years ago
Lukas Sismis	639aa04c5f	dpdk/i40e: support RSS on Intel i40e PMD driver ... Due to peculiar behavior of i40e PMD driver, the RSS is required to be set via rte_flow rules or a hash filter as compared to other NICs where RSS is configured through port configuration structure. RTE_FLOW rules are created on 5-tuples (as opposed to 3-tuple configured on the other NICs). Fragmented traffic have been tested with this setup and it has been proven that fragmented packets of the same flow are received on the same queue. At the same time, setting 3-tuple on rte_flow rules have not yield in the expected results. Notes from the experiments: - Configuration of 5-tuple (as is in the commit): fragmented and nonfragmented packets are received by the same workers even when I applied seed to alter them via tcpreplay-edit (option --seed) - Setting only ETH_RSS_FRAG_IPV4 and ETH_RSS_IPV4 (i.e. setting 3-tuple): when setting ETH_RSS_IPV4, the PMD driver says that pctype is not supported (generally this means that the "type" of traffic is not a valid configuration for the i40e) - Setting only ETH_RSS_FRAG_IPV4 and ETH_RSS_NONFRAG_IPV4_OTHER: this doesn't work well, packets of the same flow are received on the different workers (my explanation is that the fragmented packets are matched with ETH_RSS_FRAG_IPV4 but the other UDP packets are not matched with ETH_RSS_NONFRAG_IPV4_OTHER rte_flow rule (they would be matched with ETH_RSS_NONFRAG_IPV4_UDP).	4 years ago
Victor Julien	f98df5c3fd	dpdk: add RSS flags that are set in the NIC	4 years ago
Lukas Sismis	a7faed1245	dpdk: initial support with workers runmode ... Register a new runmode - DPDK. This enables a new flag on Suricata start (--dpdk). With the flag given, DPDK runmode is enabled. Runmode loads the configuration and then initializes EAL. If successful, it configures the physical NICs according to the configuration file. After that, worker threads are initialized and then are in continuous receive loop.	4 years ago