summaryrefslogtreecommitdiff
path: root/vm_sync.h
Commit message (Collapse)AuthorAgeFilesLines
* `USE_RUBY_DEBUG_LOG` doesn't check `RUBY_DEVEL`Koichi Sasada2021-12-291-1/+1
| | | | | | | | `USE_RUBY_DEBUG_LOG` was only defined when `RUBY_DEVEL` is defined. This patch removes this dependency (`USE_RUBY_DEBUG_LOG` is defined independently from `RUBY_DEVEL`). Do not commit a patch which enables `USE_RUBY_DEBUG_LOG`.
* Suppress undef warnings for USE_RUBY_DEBUG_LOGNobuyoshi Nakada2021-12-251-1/+1
|
* Adjusted indent [ci skip]Nobuyoshi Nakada2021-02-091-2/+1
|
* Fixed leaked global symbolsNobuyoshi Nakada2020-12-261-2/+4
|
* add vm_sync debug countersKoichi Sasada2020-12-161-0/+8
| | | | | | | | * vm_sync_lock * vm_sync_lock_enter * vm_sync_lock_enter_nb * vm_sync_lock_enter_cr * vm_sync_barrier
* RB_VM_LOCK_ENTER_NO_BARRIERKoichi Sasada2020-12-071-0/+13
| | | | | | | | | Write barrier requires VM lock because it accesses VM global bitmap but RB_VM_LOCK_ENTER() can invoke GC because another ractor can wait to invoke GC and RB_VM_LOCK_ENTER() is barrier point. This means that before protecting by a write barrier, GC can invoke. To prevent such situation, RB_VM_LOCK_ENTER_NO_BARRIER() is introduced. This lock primitive does not become GC barrier points.
* fix decl of ruby_single_main_ractorKoichi Sasada2020-12-071-1/+1
| | | | | | | On windows, MJIT doesn't work without this patch because of the declaration of ruby_single_main_ractor. This patch fix this issue and move the definition of it from ractor.c to vm.c to locate near place of ruby_current_vm_ptr.
* RB_VM_LOCK_ENTER_CR_LEVKoichi Sasada2020-12-071-1/+18
| | | | | This is variant of RB_VM_LOCK_ENTER_LEV, but accept current racotr's pointer.
* ruby_single_main_ractor for single ractor modeKoichi Sasada2020-12-071-2/+3
| | | | | | | | ruby_multi_ractor was a flag that indicates the interpreter doesn't make any additional ractors (single ractor mode). Instead of boolean flag, ruby_single_main_ractor pointer is introduced which keeps main ractor's pointer if single ractor mode. If additional ractors are created, ruby_single_main_ractor becomes NULL.
* remove useless semicolonsKoichi Sasada2020-10-141-2/+2
|
* relax dependencyKoichi Sasada2020-09-151-6/+8
| | | | vm_sync.h does not need to include vm_core.h and ractor_pub.h.
* check multi_ractor mode at main_pKoichi Sasada2020-09-041-2/+1
| | | | | | | | | rb_ractor_main_p() need to access to the ractor pointer in TLS. However it is slow operation so that we need to skip this check if it is not multi-ractor mode (!ruby_multi_ractor). This performance regression is pointed at https://bugs.ruby-lang.org/issues/17100#note-27
* Introduce Ractor mechanism for parallel executionKoichi Sasada2020-09-031-0/+96
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.
View Lorry Controller Status