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/3] swim suspicion
Date: Wed, 24 Apr 2019 23:21:57 +0300	[thread overview]
Message-ID: <cover.1556137229.git.v.shpilevoy@tarantool.org> (raw)

For details of the suspicion component look at the last commit. Here is a
description of the patchset in whole.

Second patch about routing is in fact the key part of the patchset. It
introduces new section in SWIM packets for routes. Route is a pair: source and
destination addresses. With help of the routing it becomes possible to send any
SWIM packets indirectly via arbitrary SWIM member to another member.

The last commit just harnesses routing section to send the same ping/ack
messages, but indirectly after several direct attempts.

Changes in V2:
- added UUID to struct swim_task;
- dropped swim_iping_block structure;
- a few changes in parameter names and comments.

V1: https://www.freelists.org/post/tarantool-patches/PATCH-06-swim-suspicion

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

Vladislav Shpilevoy (3):
  swim: store sender UUID in swim io tasks
  swim: introduce routing
  swim: introduce suspicion

 src/lib/swim/swim.c           | 148 ++++++++++++++++++++++++++++++----
 src/lib/swim/swim_constants.h |   6 ++
 src/lib/swim/swim_io.c        |  96 ++++++++++++++++++++--
 src/lib/swim/swim_io.h        |  21 ++++-
 src/lib/swim/swim_proto.c     |  84 ++++++++++++++++++-
 src/lib/swim/swim_proto.h     |  88 +++++++++++++++++++-
 test/unit/swim.c              |  76 ++++++++++++-----
 test/unit/swim.result         |  30 ++++---
 test/unit/swim_proto.c        |  56 ++++++++++++-
 test/unit/swim_proto.result   |  11 ++-
 10 files changed, 554 insertions(+), 62 deletions(-)

-- 
2.20.1 (Apple Git-117)

             reply	other threads:[~2019-04-24 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 20:21 Vladislav Shpilevoy [this message]
2019-04-24 20:21 ` [tarantool-patches] [PATCH v2 1/3] swim: store sender UUID in swim io tasks Vladislav Shpilevoy
2019-04-25 10:31   ` [tarantool-patches] " Konstantin Osipov
2019-04-24 20:21 ` [tarantool-patches] [PATCH v2 2/3] swim: introduce routing Vladislav Shpilevoy
2019-04-25 10:43   ` [tarantool-patches] " Konstantin Osipov
2019-04-25 13:50     ` Vladislav Shpilevoy
2019-04-25 13:55       ` Konstantin Osipov
2019-04-24 20:22 ` [tarantool-patches] [PATCH v2 3/3] swim: introduce suspicion Vladislav Shpilevoy
2019-04-25 10:44   ` [tarantool-patches] " Konstantin Osipov
2019-04-25 13:50 ` [tarantool-patches] Re: [PATCH v2 0/3] swim suspicion 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.1556137229.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/3] swim suspicion' \
    /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