From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v1 1/3] lib/ethdev: add ethdev op to get hash index
Date: Mon, 7 Oct 2019 04:45:50 +0000 [thread overview]
Message-ID: <MWHPR18MB16451FD05D056C4EB6A2FA48A69B0@MWHPR18MB1645.namprd18.prod.outlook.com> (raw)
In-Reply-To: <e715283a-3704-7626-f7c8-fd4f8afeb4ea@solarflare.com>
> -----Original Message-----
> From: Andrew Rybchenko <arybchenko@solarflare.com>
> Sent: Thursday, October 3, 2019 6:31 PM
> To: Vamsi Krishna Attunuru <vattunuru@marvell.com>; dev@dpdk.org
> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; ferruh.yigit@intel.com;
> thomas@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, 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 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 <vattunuru@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."
next prev parent reply other threads:[~2019-10-07 4:45 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 ` Vamsi Krishna Attunuru [this message]
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
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=MWHPR18MB16451FD05D056C4EB6A2FA48A69B0@MWHPR18MB1645.namprd18.prod.outlook.com \
--to=vattunuru@marvell.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
/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).