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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 741BF7F75C for ; Mon, 8 Sep 2014 19:32:39 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jesper.louis.andersen@gmail.com) identity=pra; client-ip=209.85.223.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jesper.louis.andersen@gmail.com"; x-sender="jesper.louis.andersen@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of jesper.louis.andersen@gmail.com designates 209.85.223.182 as permitted sender) identity=mailfrom; client-ip=209.85.223.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jesper.louis.andersen@gmail.com"; x-sender="jesper.louis.andersen@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ie0-f182.google.com) identity=helo; client-ip=209.85.223.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jesper.louis.andersen@gmail.com"; x-sender="postmaster@mail-ie0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoBAGrnDVTRVd+2m2dsb2JhbABZhDcEgni1B5k+AYENCBYQAQEBAQEGCwsJFCqDegoBAQMBEhEdARsdAQMBCwYFAwEHNwICIgERAQUBDgENBhMIGogLAQMJCJoxa4swgXKDEIkIChknDWaFdwERAQUOjz8HgnmBUwWSQYoxkzoYKYUUOy+CTwEBAQ X-IPAS-Result: ApoBAGrnDVTRVd+2m2dsb2JhbABZhDcEgni1B5k+AYENCBYQAQEBAQEGCwsJFCqDegoBAQMBEhEdARsdAQMBCwYFAwEHNwICIgERAQUBDgENBhMIGogLAQMJCJoxa4swgXKDEIkIChknDWaFdwERAQUOjz8HgnmBUwWSQYoxkzoYKYUUOy+CTwEBAQ X-IronPort-AV: E=Sophos;i="5.04,487,1406584800"; d="scan'208";a="78207046" Received: from mail-ie0-f182.google.com ([209.85.223.182]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 08 Sep 2014 19:32:38 +0200 Received: by mail-ie0-f182.google.com with SMTP id tr6so1710017ieb.13 for ; Mon, 08 Sep 2014 10:32:37 -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 :cc:content-type; bh=nRpSzO9I98JkleEhusblEddYcqG26tNRaAO1qjxkGQ0=; b=l4I5H5k5zbvH2glDIxXPqDb7svV2W85gP4YyNEeNmiwyX5F9SOKBrSCanA5HTHgtJW VZbyQKtHydZj/6UO1sU8fX27wNaRfHgtIFNmIfuhKFdxl5Z4kwAJAF+DG3DKtAWgSuEY LwMFnkTDuqiUAsIQsQ3lbi6F9T6gGDnlnmqtMx16cthiMkSUUryV7acw6BAwf1XUe6KG valhjetNvXpKQmDBviXyjwk6rviNRZYzoZDXRRAr7TKsun6u1oBR5rn28saGC9AJbSUo JCpAHM7JLwNRapT+ArH8loM/KvoVMWwD713S2l3Nk/k07hRBct32g4SmVU6BcHlR3o5f 660g== X-Received: by 10.43.172.5 with SMTP id nw5mr34201675icc.10.1410197557425; Mon, 08 Sep 2014 10:32:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.57.230 with HTTP; Mon, 8 Sep 2014 10:32:22 -0700 (PDT) In-Reply-To: References: From: Jesper Louis Andersen Date: Mon, 8 Sep 2014 19:32:22 +0200 Message-ID: To: Anil Madhavapeddy Cc: Stephen Dolan , Jiten Pathy , Caml List Content-Type: multipart/alternative; boundary=001a11c2e2b2793cb10502913401 Subject: Re: [Caml-list] Multicore runtime --001a11c2e2b2793cb10502913401 Content-Type: text/plain; charset=UTF-8 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. --001a11c2e2b2793cb10502913401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Sep 8, 2014 at 5:56 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
Indeed, our fiber model is compatible with file= system I/O, but 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 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 real= ly possible to do so.


--
J.
--001a11c2e2b2793cb10502913401--