TIPC multicast messages are currently distributed via L2 broadcast
or IP multicast to all nodes in the cluster, irrespective of the 
number of real destinations of the message.

In this series we introduce an option to transport messages via
replication ("replicast") across a selected number of unicast links,
instead of relying on the underlying media. This option is used when
true broadcast/multicast is not supported by the media, or when the
number of true destinations is much smaller than the cluster size.

v2: -Fixed a counter bug when removing nodes from destination node list
    - Moved definition of node destination list from to bcast.{h,c}

Jon Maloy (4):
  tipc: add function for checking broadcast support in bearer
  tipc: add functionality to lookup multicast destination nodes
  tipc: introduce replicast as transport option for multicast
  tipc: make replicast a user selectable option

 include/uapi/linux/tipc.h |   6 +-
 net/tipc/bcast.c          | 245 +++++++++++++++++++++++++++++++++++++++++-----
 net/tipc/bcast.h          |  40 +++++++-
 net/tipc/bearer.c         |  15 ++-
 net/tipc/bearer.h         |   6 ++
 net/tipc/link.c           |  12 ++-
 net/tipc/msg.c            |  17 ++++
 net/tipc/msg.h            |   2 +
 net/tipc/name_table.c     |  33 +++++++
 net/tipc/name_table.h     |   4 +
 net/tipc/node.c           |  27 +++--
 net/tipc/node.h           |   4 +-
 net/tipc/socket.c         |  89 ++++++++++-------
 net/tipc/udp_media.c      |   8 +-
 14 files changed, 424 insertions(+), 84 deletions(-)

-- 
2.7.4


------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to