From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id A28C17F75C for ; Tue, 9 Sep 2014 04:24:56 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yotambarnoy@gmail.com) identity=pra; client-ip=209.85.216.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yotambarnoy@gmail.com designates 209.85.216.176 as permitted sender) identity=mailfrom; client-ip=209.85.216.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qc0-f176.google.com) identity=helo; client-ip=209.85.216.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="postmaster@mail-qc0-f176.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnQBAKJkDlTRVdiwm2dsb2JhbABZhDcEgnjOWgGBDAgWEAEBAQEBBgsLCRQqhAMBAQEDARIRHQEbHgMMBgUEBw0qAgIhAQERAQUBDgENBhMiiAsBAwkImkNrizCBcoMQiToKGScNZoV3AREBBQ6NEoI0gnmBUwWaYoIQjnOERxgphS4hLwGCTgEBAQ X-IPAS-Result: AnQBAKJkDlTRVdiwm2dsb2JhbABZhDcEgnjOWgGBDAgWEAEBAQEBBgsLCRQqhAMBAQEDARIRHQEbHgMMBgUEBw0qAgIhAQERAQUBDgENBhMiiAsBAwkImkNrizCBcoMQiToKGScNZoV3AREBBQ6NEoI0gnmBUwWaYoIQjnOERxgphS4hLwGCTgEBAQ X-IronPort-AV: E=Sophos;i="5.04,489,1406584800"; d="scan'208";a="93642001" Received: from mail-qc0-f176.google.com ([209.85.216.176]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Sep 2014 04:24:55 +0200 Received: by mail-qc0-f176.google.com with SMTP id x3so3516276qcv.7 for ; Mon, 08 Sep 2014 19:24:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kGcGZpFppT8bHQ/v/5dlymWrNDE/c53SJip7Gee6WG0=; b=iLTf1v6hjP1EVmddG6HjX0lky1j95ggdPxVDuBoqNJ+y3VMUziJUK9UVM9hLM0CrN1 eLaB0Y/UbQjXcPUzzPpyKcphlxWkJzh3Ffi2O2jQMwjy5k7Dj9UbeyoxwC28T/BgqAbv sjNkbfGtjZHRBtccqFBAyVkdrnvL5K9PtKJX4YFThVmFkIJMveMZiThnFWUU9upTK5Re x9vehF7xEktgJOJpkErQatKIR/eXhFYYRjuIKHdVm55KHWsMLehMRksSSOk/+vDASyZQ ryo8+6NChHT5XNY9FUSWBGN7cxX0pZ+MUDWWSZW/rePbx/8lsbpRnvHNo4I2L8vZ1/Zh ZxiA== X-Received: by 10.140.30.74 with SMTP id c68mr44436942qgc.63.1410229494513; Mon, 08 Sep 2014 19:24:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.174.68 with HTTP; Mon, 8 Sep 2014 19:24:34 -0700 (PDT) In-Reply-To: References: From: Yotam Barnoy Date: Mon, 8 Sep 2014 22:24:34 -0400 Message-ID: To: Ocaml Mailing List Content-Type: multipart/alternative; boundary=001a113a672c12895e050298a4e7 Subject: Re: [Caml-list] Multicore runtime --001a113a672c12895e050298a4e7 Content-Type: text/plain; charset=UTF-8 I have another question about the runtime. I believe it was mentioned in the talk that there would be work-stealing between the domains. But how can we have any work-stealing when the fibers are integrated deeply inside the domains' local heaps? -Yotam On Mon, Sep 8, 2014 at 1:32 PM, Jesper Louis Andersen < jesper.louis.andersen@gmail.com> wrote: > > On Mon, Sep 8, 2014 at 5:56 PM, Anil Madhavapeddy wrote: > >> Indeed, our fiber model is compatible with filesystem I/O, but does not >> *mandate* that implementations support threads if a better-than-POSIX >> model is available on the target operating system. Async I/O works fine >> on Windows for instance, and does not require a thread-per-operation. >> > > I fully agree with this point! The trick is to take the view from fibers > and down rather than from a (specific) kernel and up. And you can easily > make this run asynchronously on systems where it is really possible to do > so. > > > -- > J. > --001a113a672c12895e050298a4e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have another question about the runtime. I believe it wa= s mentioned in the talk that there would be work-stealing between the domai= ns. But how can we have any work-stealing when the fibers are integrated de= eply inside the domains' local heaps?

-Yotam

On Mon, Sep 8= , 2014 at 1:32 PM, Jesper Louis Andersen <jesper.louis.ander= sen@gmail.com> wrote:

On Mon, Sep 8, 2014 at 5:56 PM, Anil Madhavapeddy <anil@recoil.o= rg> wrote:
Indeed, our fiber model is compatible with filesystem I/O, b= ut does not
*mandate* that implementations support threads if a better-than-POSIX
model is available on the target operating system.=C2=A0 Async I/O works fi= ne
on Windows for instance, and does not require a thread-per-operation.
=

I fully agree with this point! The trick is t= o take the view from fibers and down rather than from a (specific) kernel a= nd up. And you can easily make this run asynchronously on systems where it = is really possible to do so.=


--
J.

--001a113a672c12895e050298a4e7--