DPDK patches and discussions
 help / color / mirror / Atom feed
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 2/3] app/test: add hash index verify autotest
Date: Tue, 15 Oct 2019 17:49:41 +0100	[thread overview]
Message-ID: <a8a09422-845e-a2cb-d864-a15c32477fcd@intel.com> (raw)
In-Reply-To: <20191015095207.13249-3-vattunuru@marvell.com>

On 10/15/2019 10:52 AM, vattunuru@marvell.com wrote:
> From: Vamsi Attunuru <vattunuru@marvell.com>
> 
> Patch adds a autotest to validate rte_eth_dev_rss_hash_index_get()
> ethdev op.
> 
> Test configures the ethport in loopback mode and enables RSS for
> IP packets. The hash indices returned by those API gets validated
> by matching queue number in the reta table with the rxq(queue's idx)
> on which the packet received.

As I said implementation is not major concern, so please wait until ethdev API
discussion resolved before modifying but unit test failing me for i40e because of:
1) RSS hash function selected without checking what device is capable of, so
configuration fails.

2) rte_eth_dev_rss_reta_update() failed because of provided incompatible size

Thanks,
ferruh

> 
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>

<...>

  reply	other threads:[~2019-10-15 16:49 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] add ethdev op to get hash index 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
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 [this message]
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=a8a09422-845e-a2cb-d864-a15c32477fcd@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).