From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: olegrok@tarantool.org
Cc: v.shpilevoy@tarantool.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/4] fiber: rename ref to fiber_ref
Date: Thu, 2 Sep 2021 18:22:00 +0300 [thread overview]
Message-ID: <20210902152200.GR5743@tarantool.org> (raw)
In-Reply-To: <163ea2c0eb0172a784e29e5ea61f22e336e969a5.1628713520.git.babinoleg@mail.ru>
Oleg,
Thanks for the patch! LGTM since the changes are trivial, but consider
the nits below.
On 11.08.21, olegrok@tarantool.org wrote:
> From: Oleg Babin <babinoleg@mail.ru>
>
> Ref is a lua reference to fiber storage. This patch just renames
> storage.lua.ref to storage_ref to underline that it's not a
Minor: This line seems ambiguous (at least to me). You're writing about
storage.lua.ref, so the renamed field should be storage.lua.storage_ref.
Feel free to ignore.
> reference to fiber itself and needed only for fiber storage.
> ---
> src/lib/core/fiber.h | 2 +-
> src/lua/fiber.c | 10 +++++-----
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/src/lib/core/fiber.h b/src/lib/core/fiber.h
> index b85625ba7..593847df7 100644
> --- a/src/lib/core/fiber.h
> +++ b/src/lib/core/fiber.h
> @@ -626,7 +626,7 @@ struct fiber {
> /**
> * Optional fiber.storage Lua reference.
> */
> - int ref;
> + int storage_ref;
Typo: You're writing about <fiber_ref> in the commit subject, but the
patch is about <storage_ref>.
> } lua;
> /**
> * Iproto sync.
<snipped>
> --
> 2.32.0
>
--
Best regards,
IM
next prev parent reply other threads:[~2021-09-02 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 20:33 [Tarantool-patches] [PATCH 0/4] fiber: keep reference to userdata if fiber created once Oleg Babin via Tarantool-patches
2021-08-11 20:33 ` [Tarantool-patches] [PATCH 1/4] fiber: rename ref to fiber_ref Oleg Babin via Tarantool-patches
2021-09-02 15:22 ` Igor Munkin via Tarantool-patches [this message]
2021-09-02 18:00 ` Бабин Олег via Tarantool-patches
2021-08-11 20:33 ` [Tarantool-patches] [PATCH 2/4] fiber: pass struct fiber into lbox_pushfiber instead of id Oleg Babin via Tarantool-patches
2021-09-02 15:22 ` Igor Munkin via Tarantool-patches
2021-08-11 20:33 ` [Tarantool-patches] [PATCH 3/4] fiber: keep reference to userdata if fiber created once Oleg Babin via Tarantool-patches
2021-08-25 20:33 ` Vladislav Shpilevoy via Tarantool-patches
2021-08-26 6:14 ` Oleg Babin via Tarantool-patches
2021-09-02 15:22 ` Igor Munkin via Tarantool-patches
2021-09-02 17:59 ` Бабин Олег via Tarantool-patches
2021-09-02 21:39 ` Vladislav Shpilevoy via Tarantool-patches
2021-09-03 6:12 ` Oleg Babin via Tarantool-patches
2021-08-11 20:33 ` [Tarantool-patches] [PATCH 4/4] fiber: allocate on_stop triggers using mempool Oleg Babin via Tarantool-patches
2021-08-25 20:34 ` Vladislav Shpilevoy via Tarantool-patches
2021-08-26 6:14 ` Oleg Babin via Tarantool-patches
2021-08-26 20:01 ` Vladislav Shpilevoy via Tarantool-patches
2021-08-26 20:15 ` Oleg Babin via Tarantool-patches
2021-09-02 15:23 ` [Tarantool-patches] [PATCH 0/4] fiber: keep reference to userdata if fiber created once Igor Munkin via Tarantool-patches
2021-09-02 18:07 ` Бабин Олег via Tarantool-patches
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=20210902152200.GR5743@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=olegrok@tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 1/4] fiber: rename ref to fiber_ref' \
/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