All,
I found this peculiar thing regarding the hashing in RSS. According to the
hashing algorithm, for a particular source and destination ip address and
port numbers, the packets should be always hashed to the same queue since
the hashing algorithm uses only a fixed secret key in addition to the
On Mon, 1 Jun 2009, vikram wrote:
I found this peculiar thing regarding the hashing in RSS. According to the
hashing algorithm, for a particular source and destination ip address and
port numbers, the packets should be always hashed to the same queue since
the hashing algorithm uses only a
hhmm.. In the driver i am using, the secret key is fixed, its a constant 40
byte value.
In the RSS, after the hashing, rss looks at one indirection table (using
the hash value obtained from the hashing algo) which has the index of the
CPUs. Whichever the index that hash result in, that
I forgot to copy this to e1000-devel when I posted it to netdev.
Mike Mason
Original Message
Subject: [PATCH] e1000e: io_error_detected callback should return
PCI_ERS_RESULT_DISCONNECT on permanent failure
Date: Fri, 29 May 2009 14:16:40 -0700
From: Mike Mason mm...@us.ibm.com
On 1 Jun 2009, David Miller uttered the following:
From: Nix n...@esperi.org.uk
Date: Mon, 01 Jun 2009 01:16:26 +0100
I plan to try out 2.6.29 (and back to 2.6.25 or thereabouts) tomorrow
and see if it ever worked: if it did I'll bisect for it (rendered tricky
by the out-of-tree e1000e
On 1 Jun 2009, Jesse Brandeburg spake thusly:
57: 0 0 0 7654 0 0 0 0 PCI-MSI-edge
gordianet-rx-0
58: 0 0 0 0 8065 0 0 0 PCI-MSI-edge
gordianet-tx-0
59: 0 0 0 0 3 0 0
