diff options
| author | Koichi Sasada <ko1@atdot.net> | 2020-03-10 02:22:11 +0900 |
|---|---|---|
| committer | Koichi Sasada <ko1@atdot.net> | 2020-09-03 21:11:06 +0900 |
| commit | 79df14c04b452411b9d17e26a398e491bca1a811 (patch) | |
| tree | 7598cee0f105439efd5bb328a727b0fe27d7c666 /vm_trace.c | |
| parent | eeb5325d3bfd71301896360c17e8f51abcb9a7e5 (diff) | |
Introduce Ractor mechanism for parallel execution
This commit introduces Ractor mechanism to run Ruby program in
parallel. See doc/ractor.md for more details about Ractor.
See ticket [Feature #17100] to see the implementation details
and discussions.
[Feature #17100]
This commit does not complete the implementation. You can find
many bugs on using Ractor. Also the specification will be changed
so that this feature is experimental. You will see a warning when
you make the first Ractor with `Ractor.new`.
I hope this feature can help programmers from thread-safety issues.
Notes
Notes:
Merged: https://github.com/ruby/ruby/pull/3365
Diffstat (limited to 'vm_trace.c')
| -rw-r--r-- | vm_trace.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/vm_trace.c b/vm_trace.c index 7b39779a83..50cdf5fcde 100644 --- a/vm_trace.c +++ b/vm_trace.c @@ -1653,7 +1653,8 @@ rb_workqueue_register(unsigned flags, rb_postponed_job_func_t func, void *data) list_add_tail(&vm->workqueue, &wq_job->jnode); rb_nativethread_lock_unlock(&vm->workqueue_lock); - RUBY_VM_SET_POSTPONED_JOB_INTERRUPT(GET_EC()); + // TODO: current implementation affects only main ractor + RUBY_VM_SET_POSTPONED_JOB_INTERRUPT(rb_vm_main_ractor_ec(vm)); return TRUE; } |