From: Jon Maloy <jon.maloy@ericsson.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, parthasarathy.bhuvaragan@ericsson.com,
ying.xue@windriver.com, maloy@donjonn.com,
tipc-discussion@lists.sourceforge.net,
Jon Maloy <jon.maloy@ericsson.com>
Subject: [net-next 0/4] tipc: emulate multicast through replication
Date: Wed, 18 Jan 2017 13:50:49 -0500 [thread overview]
Message-ID: <1484765453-16258-1-git-send-email-jon.maloy@ericsson.com> (raw)
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.
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 | 200 +++++++++++++++++++++++++++++++++++++++-------
net/tipc/bcast.h | 33 +++++++-
net/tipc/bearer.c | 15 +++-
net/tipc/bearer.h | 8 +-
net/tipc/link.c | 12 ++-
net/tipc/msg.c | 17 ++++
net/tipc/msg.h | 9 +--
net/tipc/name_table.c | 38 +++++++--
net/tipc/name_table.h | 9 +++
net/tipc/node.c | 27 ++++---
net/tipc/node.h | 4 +-
net/tipc/socket.c | 61 ++++++++++----
net/tipc/udp_media.c | 8 +-
14 files changed, 374 insertions(+), 73 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-18 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 18:50 Jon Maloy [this message]
2017-01-18 18:50 ` [net-next 1/4] tipc: add function for checking broadcast support in bearer Jon Maloy
2017-01-18 18:50 ` [net-next 2/4] tipc: add functionality to lookup multicast destination nodes Jon Maloy
2017-01-18 18:50 ` [net-next 3/4] tipc: introduce replicast as transport option for multicast Jon Maloy
2017-01-18 18:50 ` [net-next 4/4] tipc: make replicast a user selectable option Jon Maloy
2017-01-20 17:10 ` [net-next 0/4] tipc: emulate multicast through replication David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1484765453-16258-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=davem@davemloft.net \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=parthasarathy.bhuvaragan@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).