From: Serge Petrenko <sergepetrenko@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>,
tarantool-patches@dev.tarantool.org, gorcunov@gmail.com
Subject: Re: [Tarantool-patches] [PATCH v2 0/4] Raft module, part 1 - explicit argument
Date: Tue, 10 Nov 2020 11:07:22 +0300 [thread overview]
Message-ID: <422d8793-253e-2008-7d59-25dfd14c6432@tarantool.org> (raw)
In-Reply-To: <cover.1604966200.git.v.shpilevoy@tarantool.org>
10.11.2020 02:58, Vladislav Shpilevoy пишет:
> The patchset is a first part of Raft movement to a separate library as
> src/lib/raft.
>
> Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-5303-p1-raft-explicit-arg
> Issue: https://github.com/tarantool/tarantool/issues/5303
>
> Changes from v1:
> - Renamed fiber.arg to fiber.f_arg;
> - Stopped using memset for raft object creation;
> - Raft global object access and validation is encapsulated into a
> single function;
> - Raft argument and runtime initialization commits are swapped.
>
> Vladislav Shpilevoy (4):
> fiber: introduce fiber.f_arg
> raft: add explicit raft argument to all functions
> raft: check box_raft is inited before usage
> vclock: move to src/lib
Hi! Thanks for the patchset!
LGTM.
>
> src/box/CMakeLists.txt | 3 -
> src/box/alter.cc | 1 -
> src/box/applier.cc | 6 +-
> src/box/box.cc | 30 +-
> src/box/error.cc | 2 +-
> src/box/gc.c | 1 -
> src/box/gc.h | 2 +-
> src/box/lua/info.c | 9 +-
> src/box/lua/init.c | 1 -
> src/box/lua/space.cc | 2 +-
> src/box/memtx_engine.c | 4 +-
> src/box/raft.c | 631 ++++++++++++++++---------------
> src/box/raft.h | 72 ++--
> src/box/recovery.h | 2 +-
> src/box/relay.cc | 2 +-
> src/box/replication.cc | 1 -
> src/box/replication.h | 2 +-
> src/box/schema.cc | 2 +-
> src/box/txn_limbo.h | 2 +-
> src/box/vy_log.c | 2 +-
> src/box/wal.c | 1 -
> src/box/wal.h | 2 +-
> src/box/xlog.h | 2 +-
> src/box/xrow.c | 1 -
> src/box/xrow.h | 2 +-
> src/lib/CMakeLists.txt | 1 +
> src/lib/core/fiber.h | 14 +-
> src/lib/vclock/CMakeLists.txt | 6 +
> src/{box => lib/vclock}/vclock.c | 0
> src/{box => lib/vclock}/vclock.h | 0
> test/unit/vclock.cc | 2 +-
> 31 files changed, 437 insertions(+), 371 deletions(-)
> create mode 100644 src/lib/vclock/CMakeLists.txt
> rename src/{box => lib/vclock}/vclock.c (100%)
> rename src/{box => lib/vclock}/vclock.h (100%)
>
--
Serge Petrenko
next prev parent reply other threads:[~2020-11-10 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 23:58 Vladislav Shpilevoy
2020-11-09 23:58 ` [Tarantool-patches] [PATCH v2 1/4] fiber: introduce fiber.f_arg Vladislav Shpilevoy
2020-11-10 7:15 ` Cyrill Gorcunov
2020-11-09 23:58 ` [Tarantool-patches] [PATCH v2 2/4] raft: add explicit raft argument to all functions Vladislav Shpilevoy
2020-11-10 7:30 ` Cyrill Gorcunov
2020-11-10 22:05 ` Vladislav Shpilevoy
2020-11-09 23:58 ` [Tarantool-patches] [PATCH v2 3/4] raft: check box_raft is inited before usage Vladislav Shpilevoy
2020-11-10 7:30 ` Cyrill Gorcunov
2020-11-09 23:58 ` [Tarantool-patches] [PATCH v2 4/4] vclock: move to src/lib Vladislav Shpilevoy
2020-11-10 7:31 ` Cyrill Gorcunov
2020-11-10 8:07 ` Serge Petrenko [this message]
2020-11-10 22:05 ` [Tarantool-patches] [PATCH v2 0/4] Raft module, part 1 - explicit argument 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=422d8793-253e-2008-7d59-25dfd14c6432@tarantool.org \
--to=sergepetrenko@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 0/4] Raft module, part 1 - explicit argument' \
/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