From: Eric Wong <normalperson@...>
Date: 2018-11-18T06:49:59+00:00
Subject: [ruby-core:89851] Re: [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe

> 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.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>