caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: Sylvain Le Gall <sylvain@le-gall.net>,
	Goswin von Brederlow <goswin-v-b@web.de>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Re: Being aware of memory overuse
Date: Wed, 10 Feb 2010 22:31:20 +0100	[thread overview]
Message-ID: <87ljf0srpz.fsf@frosties.localdomain> (raw)
In-Reply-To: <654922.88817.qm@web111503.mail.gq1.yahoo.com> (Dario Teixeira's message of "Wed, 10 Feb 2010 05:43:10 -0800 (PST)")

Dario Teixeira <darioteixeira@yahoo.com> writes:

> Hi,
>
>> I always wanted to have kernel spport for this. Some way for aplication
>> to tell the kernel about freeable memory and for the kernel to request
>> some memory to be freeed instead of swapping it out.
>
> If I recall correctly, there was an Lwn.net article reporting a lkml
> (the Linux kernel mailing list) discussion on that subject.  One of
> the proposals was for the kernel to send processes a signal (SIGFREE?)
> requesting they free up memory (by running a major GC, for example)
> whenever memory was running low.  In theory this could in some cases
> avoid the invocation of the draconian OOM killer.
>
> Question: just how effective such a feature would be in the Ocaml case?
>
> Best regards,
> Dario Teixeira

The danger of this on the other hand is that starting a mjor GC cycle
will most likely eat even more memory at first.

A signal would probably not be so helpfull. I was thinking more about a
memory preassure value. For example the kernel could provide a variable
in the vdso block saying:

0-100: You should shrink your memory usage to that many % of current
100+:  You could grow your memory to that many % of current

The kernel could consider the processes memory use, amount used for
caching in the process, other processes, general caching and the number
of hits to the pages to get a fair value for each process. and so on.

There could also be a SIGFREE signal to tell processes they must clean
up now or face the OOM killer but that would be secondary for me. I
don't ever want to see the OOM killer anyway.

MfG
        Goswin


      parent reply	other threads:[~2010-02-10 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 10:34 David Rajchenbach-Teller
2010-02-06 13:34 ` Sylvain Le Gall
2010-02-10  8:45   ` [Caml-list] " Goswin von Brederlow
2010-02-10 13:43     ` Dario Teixeira
2010-02-10 17:47       ` Sylvain Le Gall
2010-02-10 21:31       ` Goswin von Brederlow [this message]

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=87ljf0srpz.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=caml-list@inria.fr \
    --cc=darioteixeira@yahoo.com \
    --cc=sylvain@le-gall.net \
    /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).