From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, gorcunov@gmail.com, sergepetrenko@tarantool.org Subject: Re: [Tarantool-patches] [PATCH 0/2] fiber_touch() and fiber_continue() Date: Sat, 24 Apr 2021 01:16:42 +0200 [thread overview] Message-ID: <dab2dd9d-4a90-d83d-bd7b-2e8d78f9d97a@tarantool.org> (raw) In-Reply-To: <cover.1619132519.git.v.shpilevoy@tarantool.org> Please, scratch that. It was decided fiber_wakeup() in C and fiber.wakeup() in Lua must become NOP on the current fiber. See a new email thread with a different patch.
prev parent reply other threads:[~2021-04-23 23:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-22 23:05 Vladislav Shpilevoy via Tarantool-patches 2021-04-22 23:05 ` [Tarantool-patches] [PATCH 1/2] fiber: introduce fiber_touch and fiber_continue Vladislav Shpilevoy via Tarantool-patches 2021-04-22 23:05 ` [Tarantool-patches] [PATCH 2/2] fiber: use " Vladislav Shpilevoy via Tarantool-patches 2021-04-23 23:16 ` Vladislav Shpilevoy via Tarantool-patches [this message]
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=dab2dd9d-4a90-d83d-bd7b-2e8d78f9d97a@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=sergepetrenko@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/2] fiber_touch() and fiber_continue()' \ /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