Re: [RFC 0/3] low memory notify

[Colin Walters]

On Tue, 2012-01-17 at 17:13 +0900, Minchan Kim wrote:
> As you can see, it's respin of mem_notify core of KOSAKI and Marcelo.
> (Of course, KOSAKI's original patchset includes more logics but I didn't
> include all things intentionally because I want to start from beginning
> again) Recently, there are some requirements of notification of system
> memory pressure.

How does this relate to the existing cgroups memory notifications?  See
Documentation/cgroups/memory.txt under "10. OOM Control"

>  It would be very useful for various cases.
> For example, QEMU/JVM/Firefox like big memory hogger can release their memory
> when memory pressure happens.

I don't know about QEMU, but the key characteristic of the JVM and
Firefox is that they use garbage collection.  Which also applies to
Python, Ruby, Google Go, Haskell, OCaml...

So what you really want to be investigating here is integration between
a garbage collector and the system VM.  Your test program looks nothing
like a garbage collector.  I'd expect most of the performance tradeoffs
to be similar between these runtimes.  The Azul people have been doing
something like this: http://www.managedruntime.org/

In Firefox' case though it can also drop other caches, e.g.:

http://people.gnome.org/~federico/news-2007-09.html#firefox-memory-1

As far as the desktop goes, I want to get notified if we're going to hit
swap, not if we're close to exhausting the total of RAM+swap.  While
swap may make sense for servers that care about throughput mainly, I
care a lot about latency.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/