ruby.git/ext/monitor/lib, branch ruby_2_7 The Ruby Programming Language new_cond before mon_initialize 2019-12-04T04:36:41+00:00 Koichi Sasada ko1@atdot.net 2019-12-04T04:36:41+00:00 c6e3db0c66312af1e932c21006437419efa9ac75 MonitorMixin#new_cond can be called before mon_initialize, so we need to initialize `@monitor` before it. https://bugs.ruby-lang.org/issues/16255#note-4 
MonitorMixin#new_cond can be called before mon_initialize, so we
need to initialize `@monitor` before it.

https://bugs.ruby-lang.org/issues/16255#note-4
Fix documentation of `MonitorMixin#new_cond` [ci skip] (#2707) 2019-11-28T04:24:01+00:00 y-yagi yuuji.yaginuma@gmail.com 2019-11-28T04:24:01+00:00 18953416def52824c46a68370c4b34f5b720ee3f Since https://github.com/ruby/ruby/pull/2576, `new_cond` uses the Monitor object, not the receiver. 
Since https://github.com/ruby/ruby/pull/2576,
`new_cond` uses the Monitor object, not the receiver.
 Native MonitorMixin::ConditionVariable#wait 2019-10-20T06:45:30+00:00 Koichi Sasada ko1@atdot.net 2019-10-20T06:45:30+00:00 a236eaa762137d7cb32b8311e0ef9a74bbb0f385 MonitorMixin::ConditionVariable#wait can be interrupted just after Monitor#exit_for_cond. So implementation in C. 
MonitorMixin::ConditionVariable#wait can be interrupted just after
Monitor#exit_for_cond. So implementation in C.
delegate synchronize method 2019-10-20T05:21:04+00:00 Koichi Sasada ko1@atdot.net 2019-10-20T05:21:04+00:00 a0a3c701816c2fe4ab6e940c6cf5638756ceb6dc Delegate MonitorMixin#synchronize body to Monitor#synchronize. It makes guarantee interrupt safe (because Monitor#synchronize is written in C). I thought Ruby implementation is also safe, but I got stuck failure <http://ci.rvm.jp/results/trunk_test@P895/2327639> so that I introduce this fix to guarantee interrupt safe. 
Delegate MonitorMixin#synchronize body to Monitor#synchronize.
It makes guarantee interrupt safe (because Monitor#synchronize is
written in C). I thought Ruby implementation is also safe, but I
got stuck failure <http://ci.rvm.jp/results/trunk_test@P895/2327639>
so that I introduce this fix to guarantee interrupt safe.
make monitor.so for performance. (#2576) 2019-10-19T19:52:20+00:00 Koichi Sasada ko1@atdot.net 2019-10-19T19:52:20+00:00 caac5f777ae288b5982708b8690e712e1cae0cf6 Recent monitor.rb has performance problem because of interrupt handlers. 'Monitor#synchronize' is frequently used primitive so the performance of this method is important. This patch rewrite 'monitor.rb' with 'monitor.so' (C-extension) and make it faster. See [Feature #16255] for details. Monitor class objects are normal object which include MonitorMixin. This patch introduce a Monitor class which is implemented on C and MonitorMixin uses Monitor object as re-entrant (recursive) Mutex. This technique improve performance because we don't need to care atomicity and we don't need accesses to instance variables any more on Monitor class. 
Recent monitor.rb has performance problem because of interrupt
handlers. 'Monitor#synchronize' is frequently used primitive
so the performance of this method is important.

This patch rewrite 'monitor.rb' with 'monitor.so' (C-extension)
and make it faster. See [Feature #16255] for details.

Monitor class objects are normal object which include MonitorMixin.
This patch introduce a Monitor class which is implemented on C
and MonitorMixin uses Monitor object as re-entrant (recursive)
Mutex. This technique improve performance because we don't need
to care atomicity and we don't need accesses to instance variables
any more on Monitor class.