summaryrefslogtreecommitdiffstats
path: root/net/core
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2014-09-13 16:29:57 -0400
committerDavid S. Miller <davem@davemloft.net>2014-09-13 16:29:57 -0400
commit8801d48cbde6ddd275c1e6b866e434a72cafeabd (patch)
tree40b4a29e8721c329dbc2d1b2332f4beecbef45e5 /net/core
parentb25bd2515ea32cf5ddd5fd5a2a93b8c9dd875e4f (diff)
parent8c0bc550288d81e9ad8a2ed9136a72140b9ef507 (diff)
downloadlinux-8801d48cbde6ddd275c1e6b866e434a72cafeabd.tar.gz
linux-8801d48cbde6ddd275c1e6b866e434a72cafeabd.tar.bz2
linux-8801d48cbde6ddd275c1e6b866e434a72cafeabd.zip
Merge branch 'bonding-next'
Nikolay Aleksandrov says: ==================== bonding: get rid of curr_slave_lock This is the second patch-set dealing with bond locking and the purpose here is to convert curr_slave_lock into a spinlock called "mode_lock" which can be used in the various modes for their specific needs. The first three patches cleanup the use of curr_slave_lock and prepare it for the conversion which is done in patch 4 and then the modes that were using their own locks are converted to use the new "mode_lock" giving us the opportunity to remove their locks. This patch-set has been tested in each mode by running enslave/release of slaves in parallel with traffic transmission and miimon=1 i.e. running all the time. In fact this lead to the discovery of a subtle bug related to RCU which will be fixed in -net. Also did an allmodconfig test just in case :-) v2: fix bond_3ad_state_machine_handler's use of mode_lock and curr_slave_lock ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core')
0 files changed, 0 insertions, 0 deletions