On 10/10/2023 3:24 PM, Ori Kam wrote: > rte_flow supports insert by index table[1]. > > Using the above table, the application can create rules > that are based on hash. > For example application can create the following logic in order > to create load balancing: > 1. Create insert by index table with 2 rules, that hashes based on dmac > 2. Insert to index 0 a rule that sends the traffic to port A. > 3. Insert to index 1 a rule that sends the traffic to port B. > > Let's also assume that before this table, there is a 5 tuple > match table that jumps to the above table. > > So each packet that matches one of the 5 tuple rules is RSSed > to port A or B, based on dmac hash. > > The issue arises when there is a miss on the 5 tuple table, > which resulted due to the packet being the first packet of this flow, or > fragmented packet or any other reason. > In this case, the application must calculate what would be the > hash calculated by the HW so it can send the packet to the correct > port. > > This new API allows applications to calculate the hash value of a given > packet for a given table. > > [1] - > http://patches.dpdk.org/project/dpdk/patch/20230208030624.78465-2-akozy...@nvidia.com/ > > Signed-off-by: Ori Kam <or...@nvidia.com> >
Applied to dpdk-next-net/main, thanks.
