From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ABF6B7EE6C for ; Tue, 26 Nov 2013 10:15:01 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArYCAFJmlFLU4xEMnGdsb2JhbABZulmCSIMGgSkWDgEBAQEBBg0JCRQogiUBAQU6PxALGAklDwUoIYgBARa2Lh+IPxeOdgeDIIETA5gThi4Sjns X-IPAS-Result: ArYCAFJmlFLU4xEMnGdsb2JhbABZulmCSIMGgSkWDgEBAQEBBg0JCRQogiUBAQU6PxALGAklDwUoIYgBARa2Lh+IPxeOdgeDIIETA5gThi4Sjns X-IronPort-AV: E=Sophos;i="4.93,773,1378850400"; d="scan'208";a="45432850" Received: from mout.web.de ([212.227.17.12]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 26 Nov 2013 10:15:01 +0100 Received: from frosties.localnet ([37.49.32.119]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0LtFAh-1VfVIV2MuJ-012mMn for ; Tue, 26 Nov 2013 10:15:00 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.80) (envelope-from ) id 1VlEjS-0005QU-S5; Tue, 26 Nov 2013 10:14:58 +0100 Date: Tue, 26 Nov 2013 10:14:58 +0100 From: Goswin von Brederlow To: Florian Hars Cc: caml-list@inria.fr Message-ID: <20131126091458.GB20512@frosties> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> <5294457A.4020709@hars.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5294457A.4020709@hars.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V03:K0:ybkRK/qDj13K6c3ALx5Tct0vAA3NU/mdrZXoEaBrmnfH0UK9uPN /xfcSyDley/WxgWPnl8a9rMYZG2cFKdvw9ZJ9AdZYHXj1uXqxkAiHpqcSdUwNHe4Iq1JaPI ePTX8Fri+Z1TMWLR9QNnYCZvV1w3RTxMuCuezXc8/fXe/yByMCTkxjbscNVmWerXwvdolI3 uPV39kb8grEF/rlVIf9uA== Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Tue, Nov 26, 2013 at 07:53:46AM +0100, Florian Hars wrote: > Am 25.11.2013 14:55, schrieb Adrien Nader: > >As far as I know, it doesn't do overcommit. Also, I doubt that would > >change anything: if you exhaust your address space, you cannot receive a > >pointer to some place since it would collide with some of your already > >assigned space. > > That is a non-sequitur, in modern operating systems every process > gets its own space of 2^64 adresses, no matter how much physical RAM Or 2^48 on amd64 due to hardware limits. 2^47 under xen. Still plenty more than physical ram. > + swap is available. And the common way to get overcommitment (at > least on unixoids, windows may be different) in't malloc anyway, > it's fork, where both processes end up with the same address space > layout, but (logically) corresponding to differen physical memory > (modulo COW pages). > > - Florian. Note: malloc() of larger regions usualy uses mmap(), which inside the kernel sets up a COW region. So basically the same as fork(). Both are causes for overcommit. MfG Goswin