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 7CB947FA59 for ; Thu, 24 Jul 2014 01:34:40 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of raould@gmail.com) identity=pra; client-ip=209.85.219.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of raould@gmail.com designates 209.85.219.52 as permitted sender) identity=mailfrom; client-ip=209.85.219.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="raould@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-oa0-f52.google.com) identity=helo; client-ip=209.85.219.52; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="raould@gmail.com"; x-sender="postmaster@mail-oa0-f52.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsYCAFNG0FPRVds0m2dsb2JhbABZhDcEgnTPAQgWDwEBAQEBBgsLCRQphBwRHQEbHgMSEA8CJgIkAREBBQEiGxqICwEDEZlbgxJqiyiBcoMQilgKGScNZIZKEQEFDoEekR6BTgWKZ5BGkk8YKYUYHS8 X-IPAS-Result: AsYCAFNG0FPRVds0m2dsb2JhbABZhDcEgnTPAQgWDwEBAQEBBgsLCRQphBwRHQEbHgMSEA8CJgIkAREBBQEiGxqICwEDEZlbgxJqiyiBcoMQilgKGScNZIZKEQEFDoEekR6BTgWKZ5BGkk8YKYUYHS8 X-IronPort-AV: E=Sophos;i="5.01,720,1400018400"; d="scan'208";a="72598743" Received: from mail-oa0-f52.google.com ([209.85.219.52]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Jul 2014 01:34:31 +0200 Received: by mail-oa0-f52.google.com with SMTP id o6so2634767oag.39 for ; Wed, 23 Jul 2014 16:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=yke3B3qNgZFuYnnhPbJVPPVyQoDpmKU0/t6fFMzw3oQ=; b=OcG/x/1HOzt1PtjJUK+ds47r9ZslEHlAnCujCVeb6h+UT4N8r9ShDpoQD7gHHx5WQz 5faLD9FxkrNbmNQwrmB8EHeP2ts7w5YtIDsHZwX6CeXbxJkbCQsGP//VhrQ48t1gLpGU 2r99Ry0EIg2Coy5sJ/3ICfARO3dWdqEF2D+LIGKsB5Yav5c4BAP2Jw44HIFYoBcsNXsP fOZ0N0D08iydYvpCnlKPo9U29FQrhhjOCspsxebwAx/B177urfUZQ9/NuPmlp79QeIkf YBrpCBzbvN+6iaN1jnvpSLY67E3vCNKb3o3M0zHU6va8QxuCJX3P4Z8YUfKtG3QfE8tk iLuw== X-Received: by 10.60.118.8 with SMTP id ki8mr6934968oeb.29.1406158469851; Wed, 23 Jul 2014 16:34:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.76.134 with HTTP; Wed, 23 Jul 2014 16:34:09 -0700 (PDT) From: Raoul Duke Date: Wed, 23 Jul 2014 16:34:09 -0700 Message-ID: To: OCaml Content-Type: text/plain; charset=UTF-8 Subject: [Caml-list] concurrent gc? extremely clueless question warning, both generally technically but also vis-a-vie ocaml specifically: so even if ocaml can't so easily be made to support multiple threads of ocaml code, could the gc be moved off to another thread? so that it could run on another core. would that be of any benefit?