From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-2.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,SPF_PASS,T_RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 26BE61F576 for ; Tue, 20 Feb 2018 09:07:05 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id DC1A312097D; Tue, 20 Feb 2018 18:07:02 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id B219712097C for ; Tue, 20 Feb 2018 18:06:56 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 0B9981F576; Tue, 20 Feb 2018 09:06:54 +0000 (UTC) Date: Tue, 20 Feb 2018 09:06:54 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20180220090654.GA14869@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 85686 Subject: [ruby-core:85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" matz@ruby-lang.org wrote: > May I add two new candidates (IoThread and Thread::Coop)? Thanks for the ideas. I like Thread::Coop; maybe "Thread::Coro" is good, too... I don't think IoThread is good if we support Queue/Mutex/... Also, what do you think about having a way to pass options to thread creation like pthread_attr_t? ``` attr = Thread::Attr.new # similar to pthread_attr_setscope. I'm used to NPTL and # LinuxThreads only having PTHREAD_SCOPE_SYSTEM and ignored # of pthread_attr_setscope until I saw it again with mjit code: attr.type = :coop # (default is :native) # for advanced users only :) attr.vm_stack_size = ... attr.machine_stack_size = ... # This API gives room for future expansion Thread::Attr#create becomes a substitute for Thread.new attr.create(*args) # => Thread or Thread::Coop ``` And maybe we unify Thread::Coop and existing "Thread" as single public "Thread" class to Ruby API; similar to what we do with "Integer" (vs Bignum/Fixnum)