From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:89851] Re: [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe
Date: Sun, 18 Nov 2018 06:49:59 +0000 [thread overview]
Message-ID: <20181118064959.3xdgh3hcvayfhpi2@dcvr> (raw)
In-Reply-To: <redmine.issue-15316.20181118044928.b79df3c453732d72@ruby-lang.org>
> https://bugs.ruby-lang.org/issues/15316
> So it looks like we need a THREAD-SAFE (not necessarily async-safe)
> version of rb_postponed_job_register. Or a one-off API for MJIT...
> job registration for MJIT.
I think I will introduce a new "workqueue" API dedicated to
thread-safety (but not async-signal-safety). We can use the
same interrupt flag, but it will use a separate data structure.
My goal is also to support MJIT in forked processes,
because (AFAIK) some production Ruby instances use fork
with long-running processes.
next prev parent reply other threads:[~2018-11-18 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15316.20181118044928@ruby-lang.org>
2018-11-18 4:49 ` [ruby-core:89848] [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe normalperson
2018-11-18 6:49 ` Eric Wong [this message]
2018-11-18 8:09 ` [ruby-core:89852] " takashikkbn
2018-11-18 8:19 ` [ruby-core:89853] " Eric Wong
2018-11-18 8:40 ` [ruby-core:89854] " takashikkbn
2018-11-19 0:07 ` [ruby-core:89858] " takashikkbn
2018-11-19 0:22 ` [ruby-core:89859] " Eric Wong
2018-11-19 0:52 ` [ruby-core:89860] " takashikkbn
2018-11-20 1:12 ` [ruby-core:89892] " takashikkbn
2018-11-30 5:19 ` [ruby-core:90186] " takashikkbn
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181118064959.3xdgh3hcvayfhpi2@dcvr \
--to=ruby-core@ruby-lang.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).