From: Flavio Leitner <fbl@redhat.com>
To: Sathya Perla <sathya.perla@emulex.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] be2net: hash key for rss-config cmd not set
Date: Tue, 24 May 2011 10:12:31 -0300 [thread overview]
Message-ID: <4DDBAEBF.5040901@redhat.com> (raw)
In-Reply-To: <edb3e5b8-a38f-4efe-b267-9b5b332f16a4@exht1.ad.emulex.com>
On 05/24/2011 03:29 AM, Sathya Perla wrote:
> A non-zero, non-descript value is needed as the hash key. The hash variable was left un-initialized; but sometimes it gets a zero value
> and hashing is not effective. The constant value used now (not of any significance) seems to work fine.
>
> Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
> ---
> drivers/net/benet/be_cmds.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/benet/be_cmds.c b/drivers/net/benet/be_cmds.c
> index 2463b1c..81654ae 100644
> --- a/drivers/net/benet/be_cmds.c
> +++ b/drivers/net/benet/be_cmds.c
> @@ -1703,7 +1703,8 @@ int be_cmd_rss_config(struct be_adapter *adapter, u8 *rsstable, u16 table_size)
> {
> struct be_mcc_wrb *wrb;
> struct be_cmd_req_rss_config *req;
> - u32 myhash[10];
> + u32 myhash[10] = {0x0123, 0x4567, 0x89AB, 0xCDEF, 0x01EF,
> + 0x0123, 0x4567, 0x89AB, 0xCDEF, 0x01EF};
> int status;
>
> if (mutex_lock_interruptible(&adapter->mbox_lock))
I know we have the changelog saying that it's not of any significance,
but would be nice to have the same thing in the source as well.
fbl
next prev parent reply other threads:[~2011-05-24 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 6:29 [PATCH] be2net: hash key for rss-config cmd not set Sathya Perla
2011-05-24 13:12 ` Flavio Leitner [this message]
2011-05-24 17:34 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 12:25 Sathya Perla
2011-05-23 15:48 ` Ben Hutchings
2011-05-23 19:52 ` David Miller
2011-05-24 5:46 ` Sathya.Perla
2011-05-24 6:22 ` David Miller
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=4DDBAEBF.5040901@redhat.com \
--to=fbl@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.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).