public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl@eisenstein.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>,
	Thomas Hood <jdthood@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: OOM killer
Date: Fri, 28 Sep 2001 09:34:09 +0200	[thread overview]
Message-ID: <3BB427F1.5070403@eisenstein.dk> (raw)
In-Reply-To: <E15mkLX-0005S3-00@the-village.bc.nu>

Alan Cox wrote:

>>> shed:~# echo 0 >/proc/sys/vm/overcommit_memory
>>> shed:~# cat /proc/sys/vm/overcommit_memory
>>> 0
>> 
>> ahh, I see. Well, you live and learn ;)
>> 
>> I think I've got to do my research better before writing mails to lkml.
> 
> 
> In part.
> 
> The option you want is '2' which isnt implemented 8)
> 
> 0	-	I don't care
> 1	-	Use heuristics to guesstimate avoiding overcommit


Thank you for that info :)

I wrote a small test program that allocated memory in increasingly 
larger chunks, and I saw no major difference with a setting of "0" or 
"1", it seemed both settings allowed my program to allocate exactely the 
same amount of mem before ENOMEM was returned (I can send the test 
program on request).

I'll be looking forward to a setting of "2" becomming available :)


Best regards
Jesper Juhl


  reply	other threads:[~2001-09-28  7:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 16:01 OOM killer Thomas Hood
2001-09-26 17:11 ` Jesper Juhl
2001-09-27 20:52   ` Alex Bligh - linux-kernel
2001-09-26 18:06     ` Jesper Juhl
2001-09-27 23:13       ` Alan Cox
2001-09-28  7:34         ` Jesper Juhl [this message]
2001-09-28  7:54           ` Thomas Glanzmann
  -- strict thread matches above, loose matches on Subject: below --
2002-01-23 12:57 Andrey Nekrasov
2002-01-23 13:55 ` Helge Hafting
2002-02-19 10:02 Paco Martinez
2002-02-19 10:34 ` Alan Cox
2002-02-20 19:56   ` Jeffrey Nowland
2002-02-19 14:29 ` Denis Vlasenko
2005-05-26 22:37 oom killer mbneto
2005-05-28  2:52 ` John Livingston

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=3BB427F1.5070403@eisenstein.dk \
    --to=juhl@eisenstein.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jdthood@yahoo.co.uk \
    --cc=linux-kernel@alex.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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