From: Sergey Ostanevich via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] memprof: report stack resizing as internal event
Date: Mon, 29 Mar 2021 19:01:06 +0300 [thread overview]
Message-ID: <FFB9D886-ED1D-4CA8-AB67-FDA6BC85F422@tarantool.org> (raw)
In-Reply-To: <20210329083559.GL29703@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi!
Had a good time reading all your comments, thanks!
As for the reason I still not blessed this - I got good
explanation why stack resizing should be guarded for the whole
part of the code it was in original patch, so
LGTM.
Sergos
> On 29 Mar 2021, at 11:35, Igor Munkin <imun@tarantool.org> wrote:
>
> On 29.03.21, Igor Munkin wrote:
>> Sergey,
>>
>> On 29.03.21, Sergey Kaplun wrote:
>>> Igor,
>>>
>>
>> <snipped>
>>
>>>>>>
>>>>>> "Feel free to prove the opposite"(c) :)
>>>>>>
>>>>>> The current naming is much better than the previous one, but I still
>>>>>> propose to save the original on and save G(L) into a new variable.
>>>>>
>>>>> Ignoring for now.
>>>>
>>>> Well, if you just need my LGTM, you got it. I'll even push this patch by
>>>> myself. But try to hear my arguments even if they look like "bred deda".
>>>
>>> This is not about LGTM, but about a miscommunication, I hope we will
>>> understand each other's point of view and come to a consensus.
>>
>> I see no changes on the branch, hence we won't. Anyway, you have the
>> necessary amount of LGTMs, so I'll push your patch to the trunk later.
>
> Oops, seems you have only mine (at least I see no explicit LGTM from
> Sergos in the thread). Will not rush then.
>
>>
>>>
>>
>> <snipped>
>>
>>>
>>> --
>>> Best regards,
>>> Sergey Kaplun
>>
>> --
>> Best regards,
>> IM
>
> --
> Best regards,
> IM
[-- Attachment #2: Type: text/html, Size: 8703 bytes --]
next prev parent reply other threads:[~2021-03-29 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 17:54 Sergey Kaplun via Tarantool-patches
2021-03-10 14:59 ` Sergey Ostanevich via Tarantool-patches
2021-03-10 17:37 ` Sergey Kaplun via Tarantool-patches
2021-03-25 20:14 ` Igor Munkin via Tarantool-patches
2021-03-26 8:54 ` Sergey Kaplun via Tarantool-patches
2021-03-26 10:10 ` Igor Munkin via Tarantool-patches
2021-03-26 14:09 ` Sergey Kaplun via Tarantool-patches
2021-03-26 18:38 ` Igor Munkin via Tarantool-patches
2021-03-29 8:09 ` Sergey Kaplun via Tarantool-patches
2021-03-29 8:32 ` Igor Munkin via Tarantool-patches
2021-03-29 8:35 ` Igor Munkin via Tarantool-patches
2021-03-29 16:01 ` Sergey Ostanevich via Tarantool-patches [this message]
2021-03-29 20:48 ` Igor Munkin 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=FFB9D886-ED1D-4CA8-AB67-FDA6BC85F422@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=sergos@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit] memprof: report stack resizing as internal event' \
/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