From: Igor Munkin <imun@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 3/3] box: replace port_tuple with port_c everywhere Date: Mon, 27 Apr 2020 12:12:13 +0300 [thread overview] Message-ID: <20200427091213.GL11314@tarantool.org> (raw) In-Reply-To: <3a8fe601-d017-bc12-cf62-974f0177ccd1@tarantool.org> Vlad, Thanks for the fixes. On 26.04.20, Vladislav Shpilevoy wrote: > Hi! Thanks for the review! > > On 25/04/2020 02:21, Igor Munkin wrote: > > Vlad, > > > > Thanks for the patch! Please consider the comments I left below. > > > > On 23.04.20, Vladislav Shpilevoy wrote: <snipped> > >> diff --git a/src/box/port.c b/src/box/port.c > >> index 2c1fadb5c..9d9fc1dbc 100644 > >> --- a/src/box/port.c > >> +++ b/src/box/port.c > >> @@ -38,106 +38,15 @@ > >> + * result data when it fits into an object from the pool. > >> */ > >> static struct mempool port_entry_pool; > >> > >> enum { > >> - PORT_ENTRY_SIZE = MAX(sizeof(struct port_c_entry), > >> - sizeof(struct port_tuple_entry)), > >> + PORT_ENTRY_SIZE = sizeof(struct port_c_entry), > > > > Minor: PORT_ENTRY_SIZE is introduced in the first patch of the series. > > After applying these changes it looks excess. Feel free to ignore if you > > see any rationale to leave this constant. > > If I change it, I need to change its usage place too, and increase > the diff. If we want to make the diff even smaller and remove this > constant, it would be better to merge this commit and the first one. > I can do that, if you want. I see just little occurences and all: | $ grep -rnF 'PORT_ENTRY_SIZE' src | cut -f 1 -d ':' | sort | uniq -c | 5 src/box/port.c But, this comment definitely doesn't deserve merging indepentent commits. Let's leave this as is or until Nikita asks to fix it in another way. > <snipped> -- Best regards, IM
next prev parent reply other threads:[~2020-04-27 9:19 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-23 0:12 [Tarantool-patches] [PATCH v2 0/3] box_return_mp Vladislav Shpilevoy 2020-04-23 0:12 ` [Tarantool-patches] [PATCH v2 1/3] box: introduce port_c Vladislav Shpilevoy 2020-04-24 12:22 ` Igor Munkin 2020-04-24 22:06 ` Vladislav Shpilevoy 2020-04-23 0:12 ` [Tarantool-patches] [PATCH v2 2/3] box: introduce box_return_mp() public C function Vladislav Shpilevoy 2020-04-24 12:22 ` Igor Munkin 2020-04-27 15:14 ` Nikita Pettik 2020-04-27 21:29 ` Vladislav Shpilevoy 2020-04-27 22:55 ` Nikita Pettik 2020-04-23 0:12 ` [Tarantool-patches] [PATCH v2 3/3] box: replace port_tuple with port_c everywhere Vladislav Shpilevoy 2020-04-25 0:21 ` Igor Munkin 2020-04-26 19:22 ` Vladislav Shpilevoy 2020-04-27 9:12 ` Igor Munkin [this message] 2020-04-27 9:18 ` Igor Munkin 2020-04-27 14:10 ` Nikita Pettik 2020-04-28 11:08 ` [Tarantool-patches] [PATCH v2 0/3] box_return_mp Kirill Yukhin
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=20200427091213.GL11314@tarantool.org \ --to=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 3/3] box: replace port_tuple with port_c everywhere' \ /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