From: Aleksandr Lyapunov <alyapunov@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v3 13/13] tmx: use new tx manager in memtx Date: Fri, 17 Jul 2020 08:08:44 +0300 [thread overview] Message-ID: <9236c217-eaa5-28be-6e14-953b18aa0efa@tarantool.org> (raw) In-Reply-To: <dafae4b9-da65-00d4-b322-bdc4fa8c9635@tarantool.org> Hi, thanks for review! On 7/17/20 1:26 AM, Vladislav Shpilevoy wrote: > Th > 1. You can pass tx_manager_use_mvcc_engine as a second > argument to txn_can_yield() instead of adding one another > 'if'. Actually it's not so simple. It would fall in assert. > >> >> + bool could_yield = txn_has_flag(txn, TXN_CAN_YIELD); >> + if (!could_yield) >> + txn_can_yield(txn, true); > 2. This change looks unnecessary. You just added 'if'. > And still the result is that the txn can yield. See above. It's just a common restore-to-the-original state semantics. > >> >> struct memtx_engine *memtx = (struct memtx_engine *)space->engine; >> struct memtx_ddl_state state; >> @@ -940,7 +956,8 @@ memtx_space_check_format(struct space *space, struct tuple_format *format) >> iterator_delete(it); >> diag_destroy(&state.diag); >> trigger_clear(&on_replace); >> - txn_can_yield(txn, false); >> + if (!could_yield) >> + txn_can_yield(txn, false); > 3. The same. And the same in the 2 hunks below. The same! > @@ -203,6 +203,9 @@ txn_stmt_new(struct region *region) > static inline void > txn_stmt_destroy(struct txn_stmt *stmt) > { > + if (stmt->add_story != NULL || stmt->del_story != NULL) > + txm_history_rollback_stmt(stmt); > 4. Doing rollback from a destructor is totally cursed. Why are you > doing it from there? Good, replaced with assert. > >> + >> if (stmt->old_tuple != NULL) >> tuple_unref(stmt->old_tuple); >> if (stmt->new_tuple != NULL) >> diff --git a/src/box/vinyl.c b/src/box/vinyl.c >> index f9252f1..f69d3d9 100644 >> --- a/src/box/vinyl.c >> +++ b/src/box/vinyl.c >> @@ -1084,7 +1084,9 @@ vinyl_space_check_format(struct space *space, struct tuple_format *format) >> return -1; >> >> /* See the comment in vinyl_space_build_index(). */ >> - txn_can_yield(txn, true); >> + bool could_yield = txn_has_flag(txn, TXN_CAN_YIELD); >> + if (!could_yield) >> + txn_can_yield(txn, true); > 5. Unnecessary change. The same for all the other similar places. > >> >> struct trigger on_replace; >> struct vy_check_format_ctx ctx; >> @@ -1136,7 +1138,8 @@ vinyl_space_check_format(struct space *space, struct tuple_format *format) >> out: >> diag_destroy(&ctx.diag); >> trigger_clear(&on_replace); >> - txn_can_yield(txn, false); >> + if (!could_yield) >> + txn_can_yield(txn, false); >> return rc; >> } >> >> @@ -4183,7 +4186,9 @@ vinyl_space_build_index(struct space *src_space, struct index *new_index, >> * change the data dictionary, so there is no dirty state >> * that can be observed. >> */ >> - txn_can_yield(txn, true); >> + bool could_yield = txn_has_flag(txn, TXN_CAN_YIELD); >> + if (!could_yield) >> + txn_can_yield(txn, true); >> >> /* >> * Iterate over all tuples stored in the space and insert >> @@ -4284,7 +4289,8 @@ vinyl_space_build_index(struct space *src_space, struct index *new_index, >> out: >> diag_destroy(&ctx.diag); >> trigger_clear(&on_replace); >> - txn_can_yield(txn, false); >> + if (!could_yield) >> + txn_can_yield(txn, false); >> return rc; >> } >> >>
next prev parent reply other threads:[~2020-07-17 5:08 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-15 13:55 [Tarantool-patches] [PATCH v3 00/13] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 01/13] Update license file (2020) Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 02/13] Check data_offset overflow in struct tuple Aleksandr Lyapunov 2020-07-16 14:27 ` Nikita Pettik 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 03/13] vinyl: rename tx_manager -> vy_tx_manager Aleksandr Lyapunov 2020-07-15 16:04 ` Nikita Pettik 2020-07-16 8:17 ` Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 04/13] txm: introduce dirty tuples Aleksandr Lyapunov 2020-07-15 16:22 ` Nikita Pettik 2020-07-16 0:05 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 05/13] txm: save txn in txn_stmt Aleksandr Lyapunov 2020-07-15 16:23 ` Nikita Pettik 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 06/13] txm: add TX status Aleksandr Lyapunov 2020-07-15 16:42 ` Nikita Pettik 2020-07-16 0:08 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 07/13] txm: save does_require_old_tuple flag in txn_stmt Aleksandr Lyapunov 2020-07-15 16:49 ` Nikita Pettik 2020-07-16 0:09 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 08/13] txm: introduce tx manager Aleksandr Lyapunov 2020-07-15 16:51 ` Nikita Pettik 2020-07-15 22:01 ` Vladislav Shpilevoy 2020-07-16 0:10 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 09/13] tmx: introduce prepare sequence number Aleksandr Lyapunov 2020-07-15 17:13 ` Nikita Pettik 2020-07-16 0:11 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 10/13] tmx: introduce conflict tracker Aleksandr Lyapunov 2020-07-16 0:16 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 11/13] txm: introduce txm_story Aleksandr Lyapunov 2020-07-16 0:20 ` Vladislav Shpilevoy 2020-07-17 6:16 ` Aleksandr Lyapunov 2020-07-16 22:25 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 12/13] txm: clarify all fetched tuples Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 13/13] tmx: use new tx manager in memtx Aleksandr Lyapunov 2020-07-16 22:26 ` Vladislav Shpilevoy 2020-07-17 5:08 ` Aleksandr Lyapunov [this message] 2020-07-23 20:58 ` Vladislav Shpilevoy 2020-07-15 15:47 ` [Tarantool-patches] [PATCH v3 00/13] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-15 16:38 ` Aleksandr Lyapunov 2020-07-15 16:39 ` Aleksandr Lyapunov 2020-07-15 16:40 ` Aleksandr Lyapunov 2020-07-16 0:05 ` 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=9236c217-eaa5-28be-6e14-953b18aa0efa@tarantool.org \ --to=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 13/13] tmx: use new tx manager in memtx' \ /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