From: Adrien Nader <adrien@notk.org>
To: Florian Hars <florian@hars.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory
Date: Tue, 26 Nov 2013 10:24:26 +0100 [thread overview]
Message-ID: <20131126092426.GB904@notk.org> (raw)
In-Reply-To: <5294457A.4020709@hars.de>
On Tue, Nov 26, 2013, 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
> + 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).
I probably didn't make that clear: I'm only talking about 32 bit
processes. These are still very common on Windows.
Btw, you don't have fork() on Windows. Memory sharing is not done in the
same way at all.
--
Adrien Nader
next prev parent reply other threads:[~2013-11-26 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 10:52 Amogh Margoor
2013-11-20 20:56 ` Adrien Nader
2013-11-25 13:01 ` Goswin von Brederlow
2013-11-25 13:55 ` Adrien Nader
2013-11-26 6:53 ` Florian Hars
2013-11-26 9:14 ` Goswin von Brederlow
2013-11-26 9:24 ` Adrien Nader [this message]
2013-11-26 9:02 ` Goswin von Brederlow
2013-11-26 9:22 ` Adrien Nader
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 10:48 Amogh Margoor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131126092426.GB904@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=florian@hars.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox