summaryrefslogtreecommitdiffstats
path: root/net/ipv6/addrconf.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2014-04-22 21:18:26 -0400
committerDavid S. Miller <davem@davemloft.net>2014-04-22 21:18:26 -0400
commit0080d4f5f21861da5d5c0bf443e6ba1222c6af7b (patch)
tree02d52832745176ee6d63579f50d375caddd1fc62 /net/ipv6/addrconf.c
parent5a9d19ab76f98b7cdc97ba9724be01deba791bc0 (diff)
parenta8b9b96e959f3c035af20b1bd2ba67b0b7269b19 (diff)
downloadlinux-0080d4f5f21861da5d5c0bf443e6ba1222c6af7b.tar.gz
linux-0080d4f5f21861da5d5c0bf443e6ba1222c6af7b.tar.bz2
linux-0080d4f5f21861da5d5c0bf443e6ba1222c6af7b.zip
Merge branch 'tipc-next'
Ying Xue says: ==================== purge tipc_net_lock Now tipc routing hierarchy comprises the structures 'node', 'link'and 'bearer'. The whole hierarchy is protected by a big read/write lock, tipc_net_lock, to ensure that nothing is added or removed while code is accessing any of these structures. Obviously the locking policy makes node, link and bearer components closely bound together so that their relationship becomes unnecessarily complex. In the worst case, such locking policy not only has a negative influence on performance, but also it's prone to lead to deadlock occasionally. In order o decouple the complex relationship between bearer and node as well as link, the locking policy is adjusted as follows: - Bearer level RTNL lock is used on update side, and RCU is used on read side. Meanwhile, all bearer instances including broadcast bearer are saved into bearer_list array. - Node and link level All node instances are saved into two tipc_node_list and node_htable lists. The two lists are protected by node_list_lock on write side, and they are guarded with RCU lock on read side. All members in node structure including link instances are protected by node spin lock. - The relationship between bearer and node When link accesses bearer, it first needs to find the bearer with its bearer identity from the bearer_list array. When bearer accesses node, it can iterate the node_htable hash list with the node address to find the corresponding node. In the new locking policy, every component has its private locking solution and the relationship between bearer and node is very simple, that is, they can find each other with node address or bearer identity from node_htable hash list or bearer_list array. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/addrconf.c')
0 files changed, 0 insertions, 0 deletions