From: Ophir Munk <ophirmu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Yongseok Koh <yskoh@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Asaf Penso <asafp@mellanox.com>, Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: set RSS key to NULL to indicate default RSS
Date: Sat, 3 Nov 2018 17:18:13 +0000 [thread overview]
Message-ID: <VI1PR0502MB37433995BF35F7E59CF8464CD1C80@VI1PR0502MB3743.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <DB7PR05MB4426961E8417D44967F82978C3CE0@DB7PR05MB4426.eurprd05.prod.outlook.com>
Please see comments inline
> -----Original Message-----
> From: Ophir Munk
> Sent: Friday, November 02, 2018 7:55 PM
> To: dev@dpdk.org; Yongseok Koh <yskoh@mellanox.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Asaf Penso
> <asafp@mellanox.com>; Olga Shern <olgas@mellanox.com>; Ophir Munk
> <ophirmu@mellanox.com>
> Subject: FW: [PATCH v2] net/mlx5: set RSS key to NULL to indicate default
> RSS
>
>
> > -----Original Message-----
> > From: Shahaf Shuler
> > Sent: Thursday, November 01, 2018 4:01 PM
> > To: Ophir Munk <ophirmu@mellanox.com>; dev@dpdk.org; Yongseok Koh
> > <yskoh@mellanox.com>
> > Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> > <olgas@mellanox.com>; Asaf Penso <asafp@mellanox.com>
> > Subject: RE: [PATCH v2] net/mlx5: set RSS key to NULL to indicate
> > default RSS
> >
> > Hi Ophir,
> >
>
> >
> > > + if (rss->key_len == 0 && rss->key != NULL)
> > > + return rte_flow_error_set(error, ENOTSUP,
> > > +
> > > RTE_FLOW_ERROR_TYPE_ACTION_CONF,
> > > + &rss->key_len,
> > > + "RSS hash key length 0");
> > > + if (rss->key_len > 0 && rss->key_len < MLX5_RSS_HASH_KEY_LEN)
> >
> > Can't you simplify using a single condition:
> > If (rss->key && rss->key_len < MLX5_RSS_HASH_KEY_LEN)
> >
>
> Do you mean that if key==NULL we do not care about the key_len?
> (since if key==NULL key_len can have any value?
> Wil update in V3
After applying in v3 the reviewed condition code - action validation confirms a NULL key with key length 6.
But then testpmd crashes when creating the rule. Crash occurs in rte_flow_conv_action_conf().
When reverting to v2 condition code action validation is failing (as expected) with error message:
Caught error type 15 (action configuration): cause: 0x7fffffffbf18, RSS hash key too small: Unknown error 95
and flow creation fails with the same error.
I will issue v4 with v2 condition code.
>
> > Same rss->key addition should be for the case the key_len is too large.
next prev parent reply other threads:[~2018-11-03 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 17:37 [dpdk-dev] [PATCH] net/mlx5: set RSS key len 0 " Ophir Munk
2018-10-03 18:56 ` Yongseok Koh
2018-10-07 11:21 ` Shahaf Shuler
2018-10-29 16:37 ` Ophir Munk
2018-10-29 16:26 ` Ophir Munk
2018-11-01 8:59 ` [dpdk-dev] [PATCH v2] net/mlx5: set RSS key to NULL " Ophir Munk
2018-11-01 14:00 ` Shahaf Shuler
2018-11-02 17:54 ` [dpdk-dev] FW: " Ophir Munk
2018-11-03 17:18 ` Ophir Munk [this message]
2018-11-03 15:48 ` [dpdk-dev] [PATCH v3] " Ophir Munk
2018-11-03 17:39 ` [dpdk-dev] [PATCH v4] " Ophir Munk
2018-11-04 6:28 ` Shahaf Shuler
2018-11-04 10:08 ` Ophir Munk
2018-11-04 12:10 ` [dpdk-dev] [PATCH v5] " Ophir Munk
2018-11-04 13:43 ` Shahaf Shuler
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=VI1PR0502MB37433995BF35F7E59CF8464CD1C80@VI1PR0502MB3743.eurprd05.prod.outlook.com \
--to=ophirmu@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@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).