From: "Michael Chan" <mchan@broadcom.com>
To: "Jasper Spaans" <spaans@fox-it.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2 rxhash
Date: Thu, 6 Oct 2011 09:52:54 -0700 [thread overview]
Message-ID: <1317919974.8939.5.camel@HP1> (raw)
In-Reply-To: <4E8D7B85.7060702@fox-it.com>
On Thu, 2011-10-06 at 02:57 -0700, Jasper Spaans wrote:
> The data I'm processing consists of (almost 100% tcp) traffic between an
> ssl-offloader and a cluster of webservers, so the range of mac-addresses
> is rather limited. This ssl-offloader does preserve the IP-address and
> tcp ports of the clients, so if the rxhash is based on that data, it
> should be distributed evenly.
>
> Is there anything I can do about this?
>
Can you send me a small tcpdump/wireshark trace of the incoming packets?
I just need to see the tuple values in the packet headers. Thanks.
prev parent reply other threads:[~2011-10-06 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 9:57 bnx2 rxhash Jasper Spaans
2011-10-06 16:52 ` Michael Chan [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=1317919974.8939.5.camel@HP1 \
--to=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=spaans@fox-it.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).