diff options
| author |   David S. Miller <davem@davemloft.net> | 2014-11-16 15:59:19 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-11-16 15:59:19 -0500 |
| commit | 65622ed40eef5ce2732365077b22416593fec4c8 (patch) | |
| tree | 3feae5512b57c55e708107e6c191fd5d611d17f9 /drivers/net/can/c_can/c_can_platform.c | |
| parent | Merge branch 'mv88e6171_temps' (diff) | |
| parent | vmxnet3: use netdev_rss_key_fill() helper (diff) | |
| download | linux-dev-65622ed40eef5ce2732365077b22416593fec4c8.tar.xz linux-dev-65622ed40eef5ce2732365077b22416593fec4c8.zip | |
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 'drivers/net/can/c_can/c_can_platform.c')
0 files changed, 0 insertions, 0 deletions