From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
Subject: [tarantool-patches] [PATCH 0/2] swim broadcast
Date: Wed, 10 Apr 2019 20:45:32 +0300 [thread overview]
Message-ID: <cover.1554918303.git.v.shpilevoy@tarantool.org> (raw)
The patchset introduces broadcast tasks and API to broadcast pings. A ping
broadcast is useful when a cluster is just started, but UUIDs and URIs aren't
known in advance.
Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-3234-broadcast
Issue: https://github.com/tarantool/tarantool/issues/3234
Vladislav Shpilevoy (2):
swim: introduce broadcast tasks
swim: expose ping broadcast API
src/lib/swim/swim.c | 13 +++++
src/lib/swim/swim.h | 7 +++
src/lib/swim/swim_io.c | 97 +++++++++++++++++++++++++++++++
src/lib/swim/swim_io.h | 24 ++++++++
src/lib/swim/swim_transport.h | 13 +++++
src/lib/swim/swim_transport_udp.c | 17 ++++++
test/unit/swim.c | 34 ++++++++++-
test/unit/swim.result | 12 +++-
test/unit/swim_test_transport.c | 92 +++++++++++++++++++++++++++--
9 files changed, 301 insertions(+), 8 deletions(-)
--
2.17.2 (Apple Git-113)
next reply other threads:[~2019-04-10 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 17:45 Vladislav Shpilevoy [this message]
2019-04-10 17:45 ` [tarantool-patches] [PATCH 1/2] swim: introduce broadcast tasks Vladislav Shpilevoy
2019-04-11 12:57 ` [tarantool-patches] " Konstantin Osipov
2019-04-11 13:46 ` Vladislav Shpilevoy
2019-04-10 17:45 ` [tarantool-patches] [PATCH 2/2] swim: expose ping broadcast API Vladislav Shpilevoy
2019-04-11 13:00 ` [tarantool-patches] " Konstantin Osipov
2019-04-11 13:00 ` Konstantin Osipov
2019-04-11 13:47 ` Vladislav Shpilevoy
2019-04-10 18:11 ` [tarantool-patches] Re: [PATCH 0/2] swim broadcast Konstantin Osipov
2019-04-10 18:13 ` Vladislav Shpilevoy
2019-04-10 22:13 ` Vladislav Shpilevoy
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=cover.1554918303.git.v.shpilevoy@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] [PATCH 0/2] swim broadcast' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox