> -----Original Message----- > From: Andrew Rybchenko <arybche...@solarflare.com> > Sent: Thursday, October 3, 2019 6:31 PM > To: Vamsi Krishna Attunuru <vattun...@marvell.com>; dev@dpdk.org > Cc: Jerin Jacob Kollanukkaran <jer...@marvell.com>; ferruh.yi...@intel.com; > tho...@monjalon.net > Subject: [EXT] Re: [dpdk-dev] [PATCH v1 1/3] lib/ethdev: add ethdev op to get > hash index > > External Email > > ---------------------------------------------------------------------- > Hi, > > On 9/14/19 8: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 a eth_dev op to get the hash index correspond to the given > > hash value received on the given port. > > > > Some of use cases where applications would compute hash index from > > hash value upfront and it can predict the packets come to a specific > > queue. > > > > Signed-off-by: Vamsi Attunuru <vattun...@marvell.com> > > I'm sorry, but the purpose of the API and provided functionality is unclear > for > me from above description.
@Andrew, Please see the below description, if it explains the patch clearly, will send v2. " Some networking devices may use custom algos for computing hash indices and spread the packets accordingly. Patch adds a 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."
