From: Rik van Riel <riel@redhat.com>
To: "Daniel Spång" <daniel.spang@gmail.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mem notifications v2
Date: Thu, 22 Nov 2007 19:36:50 -0500 [thread overview]
Message-ID: <20071122193650.07bfe5dd@bree.surriel.com> (raw)
In-Reply-To: <cfd9edbf0711221627n55c9220dhe3d6bd44449c47b4@mail.gmail.com>
On Fri, 23 Nov 2007 01:27:38 +0100
"Daniel SpAJPYng" <daniel.spang@gmail.com> wrote:
> On 11/22/07, Rik van Riel <riel@redhat.com> wrote:
> > On Thu, 22 Nov 2007 12:23:55 +0100
> > "Daniel SpAJPYng" <daniel.spang@gmail.com> wrote:
> >
> > > When the page cache is filled, the notification is a bit early as the
> > > following example shows on a small system with 64 MB ram and no swap.
> > > On the first run the application can use 58 MB of anonymous pages
> > > before notification is sent. Then after the page cache is filled the
> > > test application is runned again and is only able to use 49 MB before
> > > being notified.
> >
> > Excellent. Throwing away useless memory when three is still
> > useful memory available sounds like a good idea.
> >
> > > I see it as a feature to be able to throw out inactive binaries and
> > > mmaped files before getting notified about low memory.
> >
> > I think that once you get low on memory, you want a bit of
> > both. Inactive binaries and mmaped files are potentially
> > useful; in-process free()d memory and caches are just as
> > potentially (dubiously) useful.
> >
> > Freeing a bit of both will probably provide a good compromise
> > between CPU and memory efficiency.
>
> I get your point, but strictly speaking, it is never freeing inactive
> binaries nor mapped files until all in-process cache are freed. But
> your argument is still valid, although a tad weaker, if you replace
> ``inactive binaries and mmaped files'' with ``page cache''.
How can you say that when you do not know how many userland
processes will get woken up, or how much memory they will
free?
The kernel sends the notification in *addition* to freeing
page cache, not instead of freeing page cache.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-11-23 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:53 Marcelo Tosatti
2007-11-22 3:07 ` kosaki
2007-11-22 17:37 ` Marcelo Tosatti
2007-11-26 11:18 ` kosaki
2007-11-22 11:23 ` Daniel Spång
2007-11-22 20:47 ` Rik van Riel
2007-11-23 0:27 ` Daniel Spång
2007-11-23 0:36 ` Rik van Riel [this message]
2007-11-23 12:42 ` Daniel Spång
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=20071122193650.07bfe5dd@bree.surriel.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.spang@gmail.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.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