From: David Miller <davem@davemloft.net>
To: mcarlson@broadcom.com
Cc: therbert@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] rps: changes to bnx2x to get device hash
Date: Wed, 11 Nov 2009 18:42:09 -0800 (PST) [thread overview]
Message-ID: <20091111.184209.197449129.davem@davemloft.net> (raw)
In-Reply-To: <20091111232103.GA1217@xw6200.broadcom.net>
From: "Matt Carlson" <mcarlson@broadcom.com>
Date: Wed, 11 Nov 2009 15:21:03 -0800
> Is a random hash key really better than arbitrary static values?
> Setting the hash key to random values means, from chip reset to chip
> reset, you could get different performance results. Unless we
> we understood how the key affects performance, I would think that
> reproducable performance numbers would be more desirable, no?
Security.
If someone knows the key and the hash function, they can purposely
pick address and port combinations that always hash to the same queue,
decresing your horsepower to handle traffic by orders of magnitude.
prev parent reply other threads:[~2009-11-12 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:53 [PATCH 2/2] rps: changes to bnx2x to get device hash Tom Herbert
2009-11-11 18:19 ` Stephen Hemminger
2009-11-11 23:21 ` Matt Carlson
2009-11-12 2:42 ` David Miller [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=20091111.184209.197449129.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).