[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1438295066-29655-1-git-send-email-jon.maloy@ericsson.com>
Date: Thu, 30 Jul 2015 18:24:14 -0400
From: Jon Maloy <jon.maloy@...csson.com>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org,
Paul Gortmaker <paul.gortmaker@...driver.com>,
erik.hugne@...csson.com, ying.xue@...driver.com, maloy@...jonn.com,
tipc-discussion@...ts.sourceforge.net,
Jon Maloy <jon.maloy@...csson.com>
Subject: [PATCH net-next 00/12] tipc: separate link aggregation from link layer
We continue the work on separating the roles of the link aggregation and
link layers, as well as making code cleanups in general.
This second commit batch focuses on moving the orchestration of link
failover and synchronization to the node level, as well as preparing the
node lock structure for further future impovements. We also make some
changes to message delivery between link and socket layer, in order to
make this mechanism safer and less obscure.
Jon Maloy (12):
tipc: eliminate function tipc_link_activate()
tipc: move all link_reset() calls to link aggregation level
tipc: reverse call order for link_reset()->node_link_down()
tipc: extend node FSM
tipc: move link synch and failover to link aggregation level
tipc: move protocol message sending away from link FSM
tipc: merge link->exec_mode and link->state into one FSM
tipc: move received discovery data evaluation inside node.c
tipc: make resetting of links non-atomic
tipc: remove implicit message delivery in node_unlock()
tipc: use temporary, non-protected skb queue for bundle reception
tipc: clean up link creation
net/tipc/bearer.c | 4 +-
net/tipc/core.h | 5 +
net/tipc/discover.c | 116 +-----
net/tipc/link.c | 1060 +++++++++++++++++++--------------------------------
net/tipc/link.h | 61 ++-
net/tipc/msg.h | 83 ++--
net/tipc/node.c | 663 ++++++++++++++++++++++++--------
net/tipc/node.h | 41 +-
8 files changed, 1009 insertions(+), 1024 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists