From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>,
tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH 2/5] qsync: add a comment about sync txn in journal allocation
Date: Fri, 10 Jul 2020 22:33:33 +0200 [thread overview]
Message-ID: <5040e7f2-6222-98d2-f058-4b2e903e758d@tarantool.org> (raw)
In-Reply-To: <20200710075605.217824-3-gorcunov@gmail.com>
On 10/07/2020 09:56, Cyrill Gorcunov wrote:
> Otherwise it is not clear why we should setup a flag here.
>
> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
> ---
> src/box/txn.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/src/box/txn.c b/src/box/txn.c
> index 49b2b2649..4251b2092 100644
> --- a/src/box/txn.c
> +++ b/src/box/txn.c
> @@ -591,6 +591,13 @@ txn_journal_entry_new(struct txn *txn)
> txn_set_flag(txn, TXN_WAIT_SYNC);
> txn_set_flag(txn, TXN_WAIT_ACK);
> } else if (!txn_limbo_is_empty(&txn_limbo)) {
> + /*
> + * There some sync entries on the
> + * fly thus wait for their completion
> + * even if this particular transaction
> + * doesn't touch sync space (each sync txn
> + * should be considered as a barrier).
> + */
> txn_set_flag(txn, TXN_WAIT_SYNC);
> }
> }
The comment is correct, but it is useless, sorry. You just
narrate what TXN_FORCE_ASYNC means. I don't see a point in
narrative comments. The code is self-explanatory already.
Я понимаю, что ты так в коде разбираешься, меняя его по чуть-чуть,
но плиз, постарайся сократить кол-во таких изменений. Они вообще
ничего не привносят кроме того, что историю затирают, и
вызывают споры вроде этого.
next prev parent reply other threads:[~2020-07-10 20:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 7:56 [Tarantool-patches] [PATCH 0/5] qsync: code cleanup Cyrill Gorcunov
2020-07-10 7:56 ` [Tarantool-patches] [PATCH 1/5] qsync: eliminate redundant writes Cyrill Gorcunov
2020-07-10 20:31 ` Vladislav Shpilevoy
2020-07-10 21:04 ` Cyrill Gorcunov
2020-07-10 7:56 ` [Tarantool-patches] [PATCH 2/5] qsync: add a comment about sync txn in journal allocation Cyrill Gorcunov
2020-07-10 20:33 ` Vladislav Shpilevoy [this message]
2020-07-10 20:34 ` Vladislav Shpilevoy
2020-07-10 21:07 ` Cyrill Gorcunov
2020-07-10 21:08 ` Vladislav Shpilevoy
2020-07-11 16:08 ` Vladislav Shpilevoy
2020-07-10 7:56 ` [Tarantool-patches] [PATCH 3/5] qsync: txn_commit_async -- drop redundant variable Cyrill Gorcunov
2020-07-10 20:35 ` Vladislav Shpilevoy
2020-07-10 21:10 ` Cyrill Gorcunov
2020-07-10 21:28 ` Vladislav Shpilevoy
2020-07-10 21:36 ` Cyrill Gorcunov
2020-07-11 14:10 ` Vladislav Shpilevoy
2020-07-11 15:18 ` Cyrill Gorcunov
2020-07-10 7:56 ` [Tarantool-patches] [PATCH 4/5] qsync: txn_commit -- use txn flag instead of caching variable Cyrill Gorcunov
2020-07-10 20:36 ` Vladislav Shpilevoy
2020-07-10 21:27 ` Cyrill Gorcunov
2020-07-10 7:56 ` [Tarantool-patches] [PATCH 5/5] qsync: sanitize txn_limbo_on_rollback Cyrill Gorcunov
2020-07-10 20:38 ` Vladislav Shpilevoy
2020-07-11 15:46 ` Cyrill Gorcunov
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=5040e7f2-6222-98d2-f058-4b2e903e758d@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 2/5] qsync: add a comment about sync txn in journal allocation' \
/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