On 10/15/2019 10:52 AM, vattun...@marvell.com wrote: > From: Vamsi Attunuru <vattun...@marvell.com> > > Some networking devices may use custom algos for computing > hash indices and spread the packets accordingly. > > Patch adds an eth_dev op to get the hash index correspond > to the given hash value received in the initial packet on > the given port. > > Some of the applications compute hash index from the hash > value received in the initial packet and than configure > the rxq to lcore mapping to make sure the mapped lcore/rxq > would receive the upcoming traffic that has similar hash. > Such applications may use these API to get the hash index > used by the PMD for spreading those traffic.
Hi Vamsi, Can you please describe this usecase? If the application is receiving the packet, it already knows which queue it is coming from, what is the benefit of the getting hash index? The concern is adding a new API which is specific to a use case and HW and won't be used in long term. That will only create technical dept for us. > > Signed-off-by: Vamsi Attunuru <vattun...@marvell.com> <...>
