[#84867] [Ruby trunk Bug#14357] thread_safe tests suite segfaults — v.ondruch@...

Issue #14357 has been reported by vo.x (Vit Ondruch).

11 messages 2018/01/15
[#85364] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults — Eric Wong <normalperson@...> 2018/02/03

[email protected] wrote:

[#84980] [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — hsbt@...

Issue #13618 has been updated by hsbt (Hiroshi SHIBATA).

10 messages 2018/01/23
[#85012] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — Eric Wong <normalperson@...> 2018/01/23

[email protected] wrote:

[ruby-core:85181] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

From: Koichi Sasada <ko1@...>
Date: 2018-01-28 14:09:42 UTC
List: ruby-core #85181
On 2018/01/25 7:01, Eric Wong wrote:
> For everything else that serves multiple clients in a single
> process, fair sharing is preferable.

Could you elaborate more? Generally, fairness is preferable. But I think 
we can document "we don't guarantee fairness scheduling on this 
feature", because our motivation is to provide a way to process multiple 
connections. Thoughts?

Or dose it cause live-lock? (no-problem on server-client apps, but 
multi-agents programs seems to cause live locking)

-- 
// SASADA Koichi at atdot dot net

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread