Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
Subject: [tarantool-patches] [PATCH v2 0/5] SWIM on_member_update
Date: Sat,  8 Jun 2019 12:31:16 +0200	[thread overview]
Message-ID: <cover.1559989748.git.v.shpilevoy@tarantool.org> (raw)

This patchset introduces API to set triggers on SWIM member updates, what
makes Lua SWIM asynchronous.

V1: https://www.freelists.org/post/tarantool-patches/PATCH-05-SWIM-on-member-update
Changes in V2:
- Renames.
- swim:delete() now waits for worker fiber join.

Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-4250-swim-triggers
Issue: https://github.com/tarantool/tarantool/issues/4250

Vladislav Shpilevoy (5):
  test: create isolated ev_loop for swim unit tests
  swim: fix a 'use after free' in SWIM tests
  swim: allow to set triggers on member updates
  swim: call swim:new/delete via Lua C, not via FFI
  swim: expose Lua triggers on member events

 extra/exports                   |   2 -
 src/CMakeLists.txt              |   3 +-
 src/lib/swim/swim.c             | 232 ++++++++++++++++++++++++----
 src/lib/swim/swim.h             |  47 +++++-
 src/lib/swim/swim_ev.c          |   6 +
 src/lib/swim/swim_ev.h          |  18 +++
 src/lib/swim/swim_io.c          |  15 +-
 src/lua/init.c                  |   2 +
 src/lua/swim.c                  | 106 +++++++++++++
 src/lua/swim.h                  |  34 +++++
 src/lua/swim.lua                | 101 +++++++++++-
 test/swim/swim.result           | 263 ++++++++++++++++++++++++++++++++
 test/swim/swim.test.lua         |  85 +++++++++++
 test/unit/swim.c                | 146 +++++++++++++++++-
 test/unit/swim.result           |  28 +++-
 test/unit/swim_test_ev.c        |  16 ++
 test/unit/swim_test_transport.c |   1 +
 test/unit/swim_test_utils.c     |  46 +++++-
 test/unit/swim_test_utils.h     |  12 ++
 19 files changed, 1107 insertions(+), 56 deletions(-)
 create mode 100644 src/lua/swim.c
 create mode 100644 src/lua/swim.h

-- 
2.20.1 (Apple Git-117)

             reply	other threads:[~2019-06-08 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 10:31 Vladislav Shpilevoy [this message]
2019-06-08 10:31 ` [tarantool-patches] [PATCH v2 1/5] test: create isolated ev_loop for swim unit tests Vladislav Shpilevoy
2019-06-08 14:32   ` [tarantool-patches] " Konstantin Osipov
2019-06-08 10:31 ` [tarantool-patches] [PATCH v2 2/5] swim: fix a 'use after free' in SWIM tests Vladislav Shpilevoy
2019-06-08 14:32   ` [tarantool-patches] " Konstantin Osipov
2019-06-08 10:31 ` [tarantool-patches] [PATCH v2 3/5] swim: allow to set triggers on member updates Vladislav Shpilevoy
2019-06-08 14:35   ` [tarantool-patches] " Konstantin Osipov
2019-06-08 10:31 ` [tarantool-patches] [PATCH v2 4/5] swim: call swim:new/delete via Lua C, not via FFI Vladislav Shpilevoy
2019-06-08 14:35   ` [tarantool-patches] " Konstantin Osipov
2019-06-08 11:04 ` [tarantool-patches] Re: [PATCH v2 0/5] SWIM on_member_update Vladislav Shpilevoy
2019-06-08 11:06   ` 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.1559989748.git.v.shpilevoy@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v2 0/5] SWIM on_member_update' \
    /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