From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Cyrill Gorcunov <gorcunov@gmail.com>, tml <tarantool-patches@dev.tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v2 2/7] wal: bind asynchronous write completion to an entry Date: Fri, 24 Jul 2020 00:10:43 +0200 [thread overview] Message-ID: <3200ccb1-1c97-54be-a034-ffae0abf09cc@tarantool.org> (raw) In-Reply-To: <20200723122942.196011-3-gorcunov@gmail.com> Hi! Thanks for the patch! See 5 comments below. On 23.07.2020 14:29, Cyrill Gorcunov wrote: > In commit 77ba0e3504464131fe81c672d508d0275be2173a we've redesigned > wal journal operations such that asynchronous write completion > is a signle instance per journal. 1. signle -> single > It turned out that such simplification is too tight and doesn't > allow us to pass entries into the journal with custom completions. > > Thus lets allow back such ability. We will need it to be able > to write "confirm" records into wal directly without touching > trasactions code at all. 2. trasactions -> transactions 3. Please, add 'Part of #5129' to the commits related to the issue. > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> > --- > diff --git a/src/box/box.cc b/src/box/box.cc > index 83eef5d98..7d61f2ed2 100644 > --- a/src/box/box.cc > +++ b/src/box/box.cc > @@ -2628,7 +2630,7 @@ box_cfg_xc(void) > } > > struct journal bootstrap_journal; > - journal_create(&bootstrap_journal, NULL, txn_complete_async, > + journal_create(&bootstrap_journal, bootstrap_journal_write, 4. Please, leave the sync write() NULL. I did it intentionally so as it would early fail if bootstrap will call blocking write anywhere. > bootstrap_journal_write); > journal_set(&bootstrap_journal); > auto bootstrap_journal_guard = make_scoped_guard([] { > diff --git a/src/box/journal.c b/src/box/journal.c > index f1e89aaa2..fb81acb39 100644 > --- a/src/box/journal.c > +++ b/src/box/journal.c > @@ -36,6 +36,7 @@ struct journal *current_journal = NULL; > > struct journal_entry * > journal_entry_new(size_t n_rows, struct region *region, > + void (*write_async_cb)(struct journal_entry *entry), 5.I think it would be better to move the callback definition to a typedef. Otherwise it looks too bulky and too many places to change, if will need to change the signature. > void *complete_data) > { > struct journal_entry *entry;
next prev parent reply other threads:[~2020-07-23 22:10 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-23 12:29 [Tarantool-patches] [PATCH v2 0/5] qsync: write CONFIRM/ROLLBACK without txn engine Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 1/7] journal: drop redundant declaration Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 2/7] wal: bind asynchronous write completion to an entry Cyrill Gorcunov 2020-07-23 22:10 ` Vladislav Shpilevoy [this message] 2020-07-24 17:48 ` Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 3/7] journal: add journal_entry_create helper Cyrill Gorcunov 2020-07-23 22:10 ` Vladislav Shpilevoy 2020-07-24 17:50 ` Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 4/7] qsync: provide a binary form of CONFIRM/ROLLBACK entries Cyrill Gorcunov 2020-07-23 22:10 ` Vladislav Shpilevoy 2020-07-24 18:07 ` Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 5/7] qsync: provide a way to encode preallocated " Cyrill Gorcunov 2020-07-23 22:10 ` Vladislav Shpilevoy 2020-07-24 18:08 ` Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 6/7] qsync: implement direct write of CONFIRM/ROLLBACK into a journal Cyrill Gorcunov 2020-07-23 22:10 ` Vladislav Shpilevoy 2020-07-24 18:16 ` Cyrill Gorcunov 2020-07-23 12:29 ` [Tarantool-patches] [PATCH v2 7/7] qsync: drop no longer used xrow_encode_confirm, rollback Cyrill Gorcunov 2020-07-23 22:13 ` [Tarantool-patches] [PATCH v2 0/5] qsync: write CONFIRM/ROLLBACK without txn engine Vladislav Shpilevoy 2020-07-24 18:16 ` 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=3200ccb1-1c97-54be-a034-ffae0abf09cc@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=gorcunov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 2/7] wal: bind asynchronous write completion to an entry' \ /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