From: "Hunt, David" <david.hunt@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Declan Doherty <declan.doherty@intel.com>,
Chas Williams <chas3@att.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Remy Horton <remy.horton@intel.com>, Ori Kam <orika@mellanox.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Radu Nicolau <radu.nicolau@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Tomasz Kantecki <tomasz.kantecki@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Jijiang Liu <jijiang.liu@intel.com>
Cc: dev@dpdk.org, Liang Ma <liang.j.ma@intel.com>,
Xueming Li <xuemingl@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] examples: fix RSS hash function configuration
Date: Wed, 20 Jun 2018 16:11:50 +0100 [thread overview]
Message-ID: <d00e6b84-ac5a-dae0-fba6-5f40d0bf69b2@intel.com> (raw)
In-Reply-To: <20180620150122.45945-1-ferruh.yigit@intel.com>
Hi Ferruh,
On 20/6/2018 4:01 PM, Ferruh Yigit wrote:
> ethdev layer introduced checks for application requested RSS hash
> functions and returns error for ones unsupported by hardware
>
> This check breaks some sample applications which blindly configures
> RSS hash functions without checking underlying hardware support.
>
> Updated examples to mask out unsupported RSS has functions during device
> configuration.
> Prints a log if configuration values updated by this check.
>
> Fixes: aa1a6d87f15d ("ethdev: force RSS offload rules again")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Return error added in this release, so no need to backport the fix to
> previous versions.
>
> Cc: David Hunt <david.hunt@intel.com>
> Cc: Liang Ma <liang.j.ma@intel.com>
> Cc: Xueming Li <xuemingl@mellanox.com>
> ---
> examples/bond/main.c | 12 ++++++++++
> examples/distributor/main.c | 11 ++++++++++
> examples/eventdev_pipeline/main.c | 11 ++++++++++
> examples/ip_pipeline/link.c | 8 +++++--
> examples/ip_reassembly/main.c | 12 ++++++++++
> examples/ipsec-secgw/ipsec-secgw.c | 12 ++++++++++
> examples/l3fwd-acl/main.c | 12 ++++++++++
> examples/l3fwd-power/main.c | 14 ++++++++++--
> examples/l3fwd-vf/main.c | 12 ++++++++++
> examples/l3fwd/main.c | 12 ++++++++++
> examples/load_balancer/init.c | 12 ++++++++++
> examples/multi_process/symmetric_mp/main.c | 12 ++++++++++
> .../performance-thread/l3fwd-thread/main.c | 12 ++++++++++
> examples/qos_meter/main.c | 22 +++++++++++++++++++
> examples/vmdq_dcb/main.c | 13 +++++++++++
> 15 files changed, 183 insertions(+), 4 deletions(-)
>
>
--snip--
I tested distributor_app, l3-fwd and l3-fwd-power, they all started OK,
giving the additional message that some flags were not available on my
hardware.
Looks good.
Regards,
Dave.
next prev parent reply other threads:[~2018-06-20 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 15:01 Ferruh Yigit
2018-06-20 15:11 ` Hunt, David [this message]
2018-06-20 17:03 ` Dan Gora
2018-06-20 17:07 ` Dan Gora
2018-06-20 17:15 ` Ferruh Yigit
2018-06-28 23:55 ` Thomas Monjalon
2018-06-29 12:54 ` Ferruh Yigit
2018-06-20 17:15 ` Ferruh Yigit
2018-06-21 16:54 ` Pavan Nikhilesh
2018-06-21 17:16 ` Ferruh Yigit
2018-06-26 17:32 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-06-29 13:54 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-07-03 16:58 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2018-07-03 18:08 ` [dpdk-dev] [PATCH v5] " Ferruh Yigit
2018-07-04 20:02 ` [dpdk-dev] [PATCH v6] " Ferruh Yigit
2018-07-05 8:17 ` Zhao, MeijuanX
2018-07-05 9:30 ` Hunt, David
2018-07-05 13:09 ` Ferruh Yigit
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=d00e6b84-ac5a-dae0-fba6-5f40d0bf69b2@intel.com \
--to=david.hunt@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chas3@att.com \
--cc=cristian.dumitrescu@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jijiang.liu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=liang.j.ma@intel.com \
--cc=orika@mellanox.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=remy.horton@intel.com \
--cc=tomasz.kantecki@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).