From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
Wei Dai <wei.dai@intel.com>, Qi Zhang <qi.z.zhang@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: force RSS offload rules again
Date: Sun, 3 Jun 2018 15:15:09 +0100 [thread overview]
Message-ID: <ddc80e16-f779-7eee-d6d4-f40f311ef3f8@intel.com> (raw)
In-Reply-To: <VI1PR05MB443154231B403543F6DD9372C3600@VI1PR05MB4431.eurprd05.prod.outlook.com>
On 6/3/2018 11:41 AM, Shahaf Shuler wrote:
> Thursday, May 31, 2018 4:23 PM, Ferruh Yigit:
>> Subject: [PATCH] ethdev: force RSS offload rules again
>>
>> PMDs should provide supported RSS hash functions via
>> dev_info.flow_type_rss_offloads variable.
>>
>> There is a check in ethdev if requested RSS hash function is supported by
>> PMD or not.
>> This check has been relaxed in previous release to not return an error when a
>> non supported has function requested [1], this has been done to not break
>> the applications.
>>
>> Adding the error return back.
>> PMDs need to provide correct list of supported hash functions and
>> applications need to take care this information before configuring the RSS
>> otherwise they will get an error from APIs:
>> rte_eth_dev_rss_hash_update()
>> rte_eth_dev_configure()
>
> Are the current app/examples in DPDK tree behave accordingly?
I tried a few which were good but I don't know about all.
That is why we should merge this patch early so that we can detect and fix ones
fails.
next prev parent reply other threads:[~2018-06-03 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 13:22 Ferruh Yigit
2018-06-03 10:41 ` Shahaf Shuler
2018-06-03 14:15 ` Ferruh Yigit [this message]
2018-06-04 7:56 ` Shahaf Shuler
2018-06-13 15:19 ` Thomas Monjalon
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=ddc80e16-f779-7eee-d6d4-f40f311ef3f8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=wei.dai@intel.com \
--cc=xuemingl@mellanox.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).