From: "Richard W.M. Jones" <rich@annexia.org>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Understanding usage by the runtime
Date: Mon, 9 Jan 2012 21:07:25 +0000 [thread overview]
Message-ID: <20120109210725.GA11759@annexia.org> (raw)
In-Reply-To: <20120109143143.GA31093@annexia.org>
While we're on the subject of mmap tricks, here's another one that may
be worth benchmarking. (The trick comes from examining the glibc
sources).
If you mmap a large contiguous area of memory that is more than you
immediately need, mmap it PROT_NONE. The reason is that Linux won't
swap out this memory. When you need to use the memory, you call
mprotect PROT_READ|PROT_WRITE (on the part that you need) and use it
as normal.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2012-01-09 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 23:45 orbitz
2011-12-31 9:11 ` David Baelde
2011-12-31 15:33 ` orbitz
2012-01-01 12:44 ` Richard W.M. Jones
2012-01-04 18:03 ` Damien Doligez
2012-01-04 18:48 ` Adrien
2012-01-04 19:37 ` John Carr
2012-01-07 5:43 ` orbitz
2012-01-08 18:45 ` Richard W.M. Jones
2012-01-08 19:00 ` Richard W.M. Jones
2012-01-08 22:33 ` Török Edwin
2012-01-09 14:31 ` Richard W.M. Jones
2012-01-09 21:07 ` Richard W.M. Jones [this message]
2012-01-08 22:50 ` orbitz
2012-01-08 23:02 ` Richard W.M. Jones
2012-01-08 23:26 ` orbitz
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=20120109210725.GA11759@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=edwintorok@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).