From: Shahaf Shuler <shahafs@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix inadequate default in RSS converter
Date: Tue, 22 May 2018 07:28:17 +0000 [thread overview]
Message-ID: <DB7PR05MB44262178C663B8366A5D8340C3940@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180521154829.6297-1-adrien.mazarguil@6wind.com>
Monday, May 21, 2018 6:50 PM, Adrien Mazarguil:
> Subject: [PATCH v2 1/2] net/mlx4: fix inadequate default in RSS converter
>
> Below commit documents 0 as a value standing for a default set of RSS hash
> types, however the mlx4 PMD doesn't interpret it correctly and still uses its
> own internal special value for that (-1).
>
> Also, its function prototype was not updated.
>
> Fixes: ac8d22de2394 ("ethdev: flatten RSS configuration in flow API")
> Fixes: 1d173da83ef2 ("net/mlx4: fix default RSS hash fields")
>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>
Series applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-05-22 7:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 15:51 [dpdk-dev] [PATCH " Adrien Mazarguil
2018-05-15 15:51 ` [dpdk-dev] [PATCH 2/2] net/mlx4: refactor RSS conversion functions Adrien Mazarguil
2018-05-17 17:46 ` Ophir Munk
2018-05-18 9:49 ` Adrien Mazarguil
2018-05-21 10:59 ` Shahaf Shuler
2018-05-21 12:23 ` Adrien Mazarguil
2018-05-21 15:50 ` [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix inadequate default in RSS converter Adrien Mazarguil
2018-05-21 15:50 ` [dpdk-dev] [PATCH v2 2/2] net/mlx4: refactor RSS conversion functions Adrien Mazarguil
2018-05-22 9:41 ` Ferruh Yigit
2018-05-22 9:58 ` Adrien Mazarguil
2018-05-22 11:26 ` [dpdk-dev] [PATCH] net/mlx4: fix undefined behavior of RSS conversion Adrien Mazarguil
2018-05-22 13:01 ` Ferruh Yigit
2018-05-22 13:21 ` Adrien Mazarguil
2018-05-22 7:28 ` Shahaf Shuler [this message]
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=DB7PR05MB44262178C663B8366A5D8340C3940@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
/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).