diff options
| author | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-08-19 00:01:08 +0000 |
|---|---|---|
| committer | normal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-08-19 00:01:08 +0000 |
| commit | d2afeb9445a3dc8445fa48f601a78c5ecd743ca6 () | |
| tree | cd66b3063bf3473dc49da879f735e88ce0436498 /thread_pthread.h | |
| parent | 77038f9f826dbc988332c9ec4abf7dea57af1160 (diff) | |
thread_pthread.c: reset timeslice delay when uncontended
This matches the behavior of old timer thread more closely and seems to fix [Bug #14999] when limited to a single CPU. I cannot reproduce the error on a multi-core system unless I use schedtool to force affinity to a single CPU: schedtool -a 0x01 -e make test-spec \ MSPECOPT='-R1000 spec/ruby/library/conditionvariable/wait_spec.rb' While it may be good enough to pass the spec, I don't have huge degree of confidence in the interrupt handling robustness under extremely heavy load (these may be ancient bugs, though). git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64467 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
| -rw-r--r-- | thread_pthread.h | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -53,6 +53,7 @@ typedef struct rb_global_vm_lock_struct { /* slow path */ struct list_head waitq; const struct rb_thread_struct *timer; /* yield */ rb_nativethread_cond_t switch_cond; |