From: Ferruh Yigit <ferruh.yigit@intel.com>
To: vattunuru@marvell.com, dev@dpdk.org
Cc: arybchenko@solarflare.com, jerinj@marvell.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v2 1/3] lib/ethdev: add ethdev op to get hash index
Date: Wed, 16 Oct 2019 18:48:52 +0100 [thread overview]
Message-ID: <2bf3e6cb-e646-d4f3-774f-d9df750ac842@intel.com> (raw)
In-Reply-To: <20191015095207.13249-2-vattunuru@marvell.com>
On 10/15/2019 10:52 AM, vattunuru@marvell.com wrote:
> From: Vamsi Attunuru <vattunuru@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.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
<...>
> @@ -364,6 +364,10 @@ typedef int (*rss_hash_conf_get_t)(struct rte_eth_dev *dev,
> struct rte_eth_rss_conf *rss_conf);
> /**< @internal Get current RSS hash configuration of an Ethernet device */
>
> +typedef int (*rss_hash_index_get_t)(struct rte_eth_dev *dev,
> + uint32_t hash, uint32_t *hash_idx);
> +/**< @internal Get RSS hash id of given hash value */
s/hash id/hash index/ ?
next prev parent reply other threads:[~2019-10-16 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 5:52 [dpdk-dev] [PATCH v1 0/3] " vattunuru
2019-09-14 5:52 ` [dpdk-dev] [PATCH v1 1/3] lib/ethdev: " vattunuru
2019-10-03 13:00 ` Andrew Rybchenko
2019-10-07 4:45 ` [dpdk-dev] [EXT] " Vamsi Krishna Attunuru
2019-10-15 9:52 ` [dpdk-dev] [PATCH v2 0/3] " vattunuru
2019-10-15 9:52 ` [dpdk-dev] [PATCH v2 1/3] lib/ethdev: " vattunuru
2019-10-15 16:47 ` Ferruh Yigit
2019-10-15 17:28 ` Vamsi Krishna Attunuru
2019-10-16 17:47 ` Ferruh Yigit
2019-10-16 17:48 ` Ferruh Yigit [this message]
2019-10-15 9:52 ` [dpdk-dev] [PATCH v2 2/3] app/test: add hash index verify autotest vattunuru
2019-10-15 16:49 ` Ferruh Yigit
2019-10-15 9:52 ` [dpdk-dev] [PATCH v2 3/3] net/octeontx2: add eth dev op callback to get hash index vattunuru
2019-09-14 5:52 ` [dpdk-dev] [PATCH v1 2/3] app/test: add hash index verify autotest vattunuru
2019-09-14 5:52 ` [dpdk-dev] [PATCH v1 3/3] net/octeontx2: add eth dev op callback to get hash index vattunuru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2bf3e6cb-e646-d4f3-774f-d9df750ac842@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
--cc=vattunuru@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).