From: "Lluís Batlle i Rossell" <viriketo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Swap considered harmful (Sorry)
Date: Mon, 7 Aug 2006 19:49:05 +0200 [thread overview]
Message-ID: <44D77D11.5080904@gmail.com> (raw)
In-Reply-To: <44B66FCA.3040308@lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Ronald G Minnich wrote:
> Charles Forsyth wrote:
>
>>
>> Linux apparently takes the Atlas approach and thrashes on demand.
>>
>
> until it starts killing random processes. Usually the wrong one. But,
> hey, heuristics, right?
Maybe you already know, but by change I got into the linux malloc(3)
manpage, and I found its BUGS section:
BUGS
By default, Linux follows an optimistic memory allocation
strategy.
This means that when malloc() returns non-NULL there is no
guarantee
that the memory really is available. This is a really bad bug.
In case
it turns out that the system is out of memory, one or more
processes
will be killed by the infamous OOM killer. In case Linux is
employed
under circumstances where it would be less desirable to
suddenly lose
some randomly picked processes, and moreover the kernel version
is suf-
ficiently recent, one can switch off this overcommitting behavior
using
a command like
# echo 2 > /proc/sys/vm/overcommit_memory
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]
next prev parent reply other threads:[~2006-08-07 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 13:52 Brantley Coile
2006-07-13 14:06 ` Charles Forsyth
2006-07-13 16:07 ` Ronald G Minnich
2006-07-13 16:08 ` quanstro
2006-07-14 11:10 ` Paweł Lasek
2006-07-14 11:54 ` quanstro
2006-07-14 19:40 ` Paweł Lasek
2006-08-07 17:49 ` Lluís Batlle i Rossell [this message]
2006-08-07 18:13 ` Sascha Retzki
2006-07-13 16:09 ` Ronald G Minnich
2006-07-13 16:07 ` quanstro
2006-07-13 17:05 ` David Leimbach
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=44D77D11.5080904@gmail.com \
--to=viriketo@gmail.com \
--cc=9fans@cse.psu.edu \
/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).