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] fiber: destroy fiber.storage created by iproto Date: Fri, 13 Dec 2019 16:35:14 +0300 [thread overview] Message-ID: <20191213133514.GN1214@tarantool.org> (raw) In-Reply-To: <1d40cedb-c631-a420-2391-1f27a5a07fe5@tarantool.org> Vlad, On 13.12.19, Vladislav Shpilevoy wrote: > Thanks for the review! > <snipped> > > > > >> /* reset pending wakeups */ > >> rlist_del(&fiber->state); > >> if (! (fiber->flags & FIBER_IS_JOINABLE)) > >> diff --git a/src/lib/core/fiber.h b/src/lib/core/fiber.h > >> index c5b975513..21fff8f88 100644 > >> --- a/src/lib/core/fiber.h > >> +++ b/src/lib/core/fiber.h > >> @@ -458,8 +458,17 @@ struct fiber { > >> > >> /** Triggers invoked before this fiber yields. Must not throw. */ > >> struct rlist on_yield; > >> - /** Triggers invoked before this fiber stops. Must not throw. */ > >> - struct rlist on_stop; > >> + /** > >> + * Triggers invoked before this fiber is > >> + * stopped/reset/recycled/destroyed/reused. In other > >> + * words, each time when the fiber has finished execution > >> + * of a request. > >> + * In particular, for fibers not from fiber pool the > >> + * cleanup is done before destroy and death. > >> + * Pooled fibers are cleaned up after each request, even > >> + * if they are never destroyed. > >> + */ > >> + struct rlist on_cleanup; > > > > Minor: both trigger lists above has the "Must not throw" note. Does the > > introduced list respect this rule? Please, adjust the comment if yes. > > Nope. These 'must not throw' are outdated. Our triggers does not > throw errors anymore by design. So I deleted it from the updated > comment. > OK, thanks, now it's clear. Guess we need an activity to update comments for other trigger lists. -- Best regards, IM
next prev parent reply other threads:[~2019-12-13 13:37 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-08 19:28 [Tarantool-patches] [PATCH 0/2] Fiber storage leak Vladislav Shpilevoy 2019-12-08 19:28 ` [Tarantool-patches] [PATCH 1/2] fiber: unref fiber.storage via global Lua state Vladislav Shpilevoy 2019-12-11 23:57 ` Igor Munkin 2019-12-12 8:50 ` Konstantin Osipov 2019-12-12 23:38 ` Vladislav Shpilevoy 2019-12-13 10:44 ` Igor Munkin 2019-12-08 19:28 ` [Tarantool-patches] [PATCH 2/2] fiber: destroy fiber.storage created by iproto Vladislav Shpilevoy 2019-12-09 7:21 ` Konstantin Osipov 2019-12-09 23:31 ` Vladislav Shpilevoy 2019-12-10 8:21 ` Konstantin Osipov 2019-12-10 8:32 ` Konstantin Osipov 2019-12-10 22:59 ` Vladislav Shpilevoy 2019-12-11 7:08 ` Konstantin Osipov 2019-12-11 21:23 ` Vladislav Shpilevoy 2019-12-12 0:00 ` Igor Munkin 2019-12-12 23:37 ` Vladislav Shpilevoy 2019-12-13 13:35 ` Igor Munkin [this message] 2019-12-12 8:46 ` Konstantin Osipov 2019-12-13 0:02 ` Vladislav Shpilevoy 2019-12-13 7:58 ` Konstantin Osipov 2019-12-13 23:11 ` Vladislav Shpilevoy 2019-12-14 12:26 ` Konstantin Osipov 2019-12-14 12:30 ` Konstantin Osipov 2019-12-14 12:33 ` Konstantin Osipov 2019-12-14 16:49 ` Vladislav Shpilevoy 2019-12-14 20:59 ` Vladislav Shpilevoy
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=20191213133514.GN1214@tarantool.org \ --to=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/2] fiber: destroy fiber.storage created by iproto' \ /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