From: David Miller <davem@davemloft.net>
To: Jon.Zhou@jdsu.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: packet received in a wrong rx-queue?
Date: Wed, 18 May 2011 23:36:14 -0400 (EDT) [thread overview]
Message-ID: <20110518.233614.1134947771941589398.davem@davemloft.net> (raw)
In-Reply-To: <4A6A2125329CFD4D8CC40C9E8ABCAB9F250D7491A8@MILEXCH2.ds.jdsu.net>
From: Jon Zhou <Jon.Zhou@jdsu.com>
Date: Wed, 18 May 2011 20:22:07 -0700
> form the 82599 datasheet, the hash algorithm is consist of src/dst
> ip, src/dst port,protocol why it got different hash value with same
> ip/port pair?
The same reason why feeding different sets of discrete 32-bit and
16-bit values to a cryptographic hash results in a different final
hash value.
Our software RPS/RFS implementation used to have this quality too.
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2011-05-19 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 9:00 packet received in a wrong rx-queue? Jon Zhou
2011-05-18 9:13 ` David Miller
2011-05-19 1:26 ` Jon Zhou
2011-05-19 1:32 ` David Miller
2011-05-19 3:22 ` Jon Zhou
2011-05-19 3:36 ` David Miller [this message]
2011-05-20 1:48 ` Jon Zhou
2011-05-20 3:12 ` 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=20110518.233614.1134947771941589398.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jon.Zhou@jdsu.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.