From: Or Gerlitz <ogerlitz@mellanox.com>
To: Eyal perry <eyalpe@dev.mellanox.co.il>, Eyal Perry <eyalpe@mellanox.com>
Cc: Amir Vadai <amirv@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Ben Hutchings <ben@decadent.org.uk>, <netdev@vger.kernel.org>,
"Yevgeny Petrilin" <yevgenyp@mellanox.com>
Subject: Re: [PATCH net-next 2/2] net/mlx4_en: Support for configurable RSS hash function
Date: Wed, 5 Nov 2014 15:30:12 +0200 [thread overview]
Message-ID: <545A2664.7040001@mellanox.com> (raw)
In-Reply-To: <545A20B0.4080807@dev.mellanox.co.il>
On 11/5/2014 3:05 PM, Eyal perry wrote:
> On 11/5/2014 2:27 PM, Or Gerlitz wrote:
>>> +
>>> +static int mlx4_en_set_rxfh_func(struct net_device *dev, u32 hfunc)
>>> +{
>>> + struct mlx4_en_priv *priv = netdev_priv(dev);
>>> + struct mlx4_en_dev *mdev = priv->mdev;
>>> + u32 prev_rss_hash_fn = priv->rss_hash_fn;
>>> + int err = 0;
>>> +
>>> + if (!(hfunc & priv->rss_hash_fn_caps))
>>> + return -EINVAL;
>>> +
>>> + priv->rss_hash_fn = hfunc;
>> Seems that you are blindly setting here priv->rss_hash_fn to the function (xor or top) requested by the user w.o prior checking if the firmware actually supports that
>> (e.g test it against priv->rss_hash_fn_caps, right?
>>
> That exactly what I do 3 lines above, priv->rss_hash_fn_caps is derived from firmware capabilities.
got it, thanks.
>
> [...]
>
>>> --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c
>>> +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c
>>> @@ -1113,10 +1113,13 @@ int mlx4_en_config_rss_steer(struct
>>> mlx4_en_priv *priv)
>>> }
>>> rss_context->flags = rss_mask;
>>> - rss_context->hash_fn = MLX4_RSS_HASH_TOP;
>>> - for (i = 0; i < 10; i++)
>>> - rss_context->rss_key[i] = cpu_to_be32(rsskey[i]);
>>> -
>>> + if (priv->rss_hash_fn & MLX4_RSS_HASH_XOR) {
>>> + rss_context->hash_fn = MLX4_RSS_HASH_XOR;
>>> + } else {
>>> + rss_context->hash_fn = MLX4_RSS_HASH_TOP;
>>> + for (i = 0; i < 10; i++)
>>> + rss_context->rss_key[i] = cpu_to_be32(rsskey[i]);
>>> + }
>> So this patch effectively changes the default from top to xor, right? is
>> that intentional? if yes, spare few words on the change log.
>>
> No, in general the default shouldn't be affected by the patch (unless
> there's a bug). The default value is set in mlx4_en_init_netdev() and it
> will remain Toeplitz unless firmware is supports only XOR hash function.
>
Oh, I see why I was confused and what I think need to be fixed. You are
using both MLX4_RSS_HASH_TOP/XOR and RSS_HASH_TOP/XOR, any reason for that?
Also, priv->rss_hash_fn should equal one value, right? so this code "if
(priv->rss_hash_fn & something)" is confusing, should be "if
(priv->rss_hash_fn == something)"
Or.
next prev parent reply other threads:[~2014-11-05 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 11:59 [PATCH net-next 0/2] ethtool, net/mlx4_en: RSS hash function selection Amir Vadai
2014-11-05 11:59 ` [PATCH net-next 1/2] ethtool: Support for configurable RSS hash function Amir Vadai
2014-11-05 21:51 ` Ben Hutchings
2014-11-06 9:41 ` Eyal perry
2014-11-05 11:59 ` [PATCH net-next 2/2] net/mlx4_en: " Amir Vadai
2014-11-05 12:27 ` Or Gerlitz
2014-11-05 13:05 ` Eyal perry
2014-11-05 13:30 ` Or Gerlitz [this message]
2014-11-05 13:48 ` Eyal perry
2014-11-05 13:53 ` Or Gerlitz
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=545A2664.7040001@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=amirv@mellanox.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=eyalpe@dev.mellanox.co.il \
--cc=eyalpe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@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).