summaryrefslogtreecommitdiffstats
path: root/net/can
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2014-11-16 15:59:19 -0500
committerDavid S. Miller <davem@davemloft.net>2014-11-16 15:59:19 -0500
commit65622ed40eef5ce2732365077b22416593fec4c8 (patch)
tree3feae5512b57c55e708107e6c191fd5d611d17f9 /net/can
parentca245024349c0d44434a6381583b99f0eb559c7c (diff)
parent6bf79cdddd50e90cbba7471623c129dadf9c873b (diff)
downloadop-kernel-dev-65622ed40eef5ce2732365077b22416593fec4c8.zip
op-kernel-dev-65622ed40eef5ce2732365077b22416593fec4c8.tar.gz
Merge branch 'rss_key_fill'
Eric Dumazet says: ==================== net: provide common RSS key infrastructure RSS (Receive Side Scaling) uses a 40 bytes key to provide hash for incoming packets to select appropriate incoming queue on NIC. Hash algo (Toeplitz) is also well known and documented by Microsoft (search for "Verifying the RSS Hash Calculation") Problem is that some drivers use a well known key. It makes very easy for attackers to target one particular RX queue, knowing that number of RX queues is a power of two, or at least some small number. Other drivers use a random value per port, making difficult tuning on bonding setups. Lets add a common infrastructure, so that host gets an unique RSS key, and drivers do not have to worry about this. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/can')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud