From: Igor Munkin <imun@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 2/2] box: reduce box_process_lua Lua GC memory usage Date: Sun, 21 Jun 2020 22:09:24 +0300 [thread overview] Message-ID: <20200621190924.GD3503@tarantool.org> (raw) In-Reply-To: <9d73cfb2-99f5-1d1c-b337-3858b697c631@tarantool.org> Vlad, On 21.06.20, Vladislav Shpilevoy wrote: > > diff --git a/src/box/lua/call.c b/src/box/lua/call.c > > index e1b1a5e81..e52f16ca4 100644 > > --- a/src/box/lua/call.c > > +++ b/src/box/lua/call.c > > @@ -48,6 +48,15 @@ > > #include "mpstream/mpstream.h" > > #include "box/session.h" > > > > +/* > > Please, change to /**. In out of function comments we use /** > as a comment start. Yes, it's mentioned in commenting example[1] but I see license comment doesn't conform these guidelines. Nevertheless, I fixed, squashed, force-pushed to the branch. Diff is below: ================================================================================ diff --git a/src/box/lua/call.c b/src/box/lua/call.c index e52f16ca4..c3c60a4aa 100644 --- a/src/box/lua/call.c +++ b/src/box/lua/call.c @@ -48,7 +48,7 @@ #include "mpstream/mpstream.h" #include "box/session.h" -/* +/** * Handlers identifiers to obtain lua_Cfunction reference from * Lua registry table. These handlers are initialized on Tarantool * startup and are used until the Lua universe is destroyed. ================================================================================ > > > + * Handlers identifiers to obtain lua_Cfunction reference from > > + * Lua registry table. These handlers are initialized on Tarantool > > + * startup and are used until the Lua universe is destroyed. > > + * Such approach reduces Lua GC usage since there is no need to > > + * create short-lived GCfunc objects for the corresponding C > > + * function on each iproto CALL/EVAL request or stored Lua > > + * procedure call. > > + */ [1]: https://www.tarantool.io/en/doc/2.3/dev_guide/c_style_guide/#commenting-style -- Best regards, IM
next prev parent reply other threads:[~2020-06-21 19:18 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-19 20:50 [Tarantool-patches] [PATCH 0/2] Reduce Lua GC pressure in Tarantool Igor Munkin 2020-06-19 20:40 ` [Tarantool-patches] [PATCH 1/2] test: disable JIT for Lua Fun totable function Igor Munkin 2020-06-21 10:26 ` Sergey Ostanevich 2020-06-21 20:24 ` Igor Munkin 2020-06-25 9:43 ` Sergey Ostanevich 2020-06-26 11:11 ` Igor Munkin 2020-06-26 13:11 ` Igor Munkin 2020-06-23 18:04 ` Igor Munkin 2020-06-23 18:45 ` Alexander V. Tikhonov 2020-06-23 21:58 ` Igor Munkin 2020-06-19 20:40 ` [Tarantool-patches] [PATCH 2/2] box: reduce box_process_lua Lua GC memory usage Igor Munkin 2020-06-20 17:42 ` Vladislav Shpilevoy 2020-06-20 21:24 ` Igor Munkin 2020-06-21 10:27 ` Sergey Ostanevich 2020-06-21 10:40 ` Igor Munkin 2020-06-21 15:35 ` Vladislav Shpilevoy 2020-06-21 19:09 ` Igor Munkin [this message] 2020-06-22 22:54 ` [Tarantool-patches] [PATCH 0/2] Reduce Lua GC pressure in Tarantool Vladislav Shpilevoy 2020-06-23 21:06 ` Vladislav Shpilevoy 2020-06-23 21:58 ` Igor Munkin 2020-06-23 21:59 ` Igor Munkin 2020-06-27 13:22 ` Igor Munkin
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=20200621190924.GD3503@tarantool.org \ --to=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/2] box: reduce box_process_lua Lua GC memory usage' \ /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