From: "Daniel Spång" <daniel.spang@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
linux-mm@kvack.org, drepper@redhat.com,
akpm@linux-foundation.org, mbligh@mbligh.org,
balbir@linux.vnet.ibm.com, 7eggert@gmx.de
Subject: Re: [RFC Patch] Thrashing notification
Date: Tue, 6 Nov 2007 11:41:20 +0100 [thread overview]
Message-ID: <cfd9edbf0711060241i7ad7e058m3e6795d90c4da82b@mail.gmail.com> (raw)
In-Reply-To: <20071105151723.71b3faaf@bree.surriel.com>
On 11/5/07, Rik van Riel <riel@redhat.com> wrote:
> On Mon, 5 Nov 2007 13:30:25 -0500
> Marcelo Tosatti <marcelo@kvack.org> wrote:
>
> > Hooking into try_to_free_pages() makes the scheme suspectible to
> > specifics such as:
>
> The specific of where the hook is can be changed. I am sure the
> two of you can come up with the best way to do things. Just keep
> shooting holes in each other's ideas until one idea remains which
> neither of you can find a problem with[1] :)
>
> > Remember that notifications are sent to applications which can allocate
> > globally...
>
> This is the bigger problem with the sysfs code: every task that
> watches the sysfs node will get woken up. That could be a big
> problem when there are hundreds of processes watching that file.
>
> Marcelo's code, which only wakes up one task at a time, has the
> potential to work much better. That code can also be enhanced
> to wake up tasks that use a lot of memory on the specific NUMA
> node that has a memory shortage.
>
> [1] Yes, that is how I usually come up with VM ideas :)
I have actually no problem at all using a device to get the message to
userspace. My patch was more like a demonstration of when to trigger
the notification. I still (obviously) think that we need a
notification for systems without swap too.
A concern, or feature =), with the notify-on-swap method is that with
responsive user applications, it will never use swap at all. There are
for sure systems where this behavior is desirable, but for example
desktop systems, the memory occupied by inactive processes might be
better used by active ones.
I think there is a need for both notifications, first a notification
when we are about to swap and then one to trigger when the total free
vm is low or when the system is thrashing, preferable using the same
notification method.
--
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-06 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 14:47 Daniel Spång
2007-11-05 15:43 ` Daniel Spång
2007-11-05 18:30 ` Marcelo Tosatti
2007-11-05 20:17 ` Rik van Riel
2007-11-06 10:41 ` Daniel Spång [this message]
2007-11-06 20:01 ` Rik van Riel
2007-11-06 21:27 ` Daniel Spång
2007-11-06 10:36 ` 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=cfd9edbf0711060241i7ad7e058m3e6795d90c4da82b@mail.gmail.com \
--to=daniel.spang@gmail.com \
--cc=7eggert@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=drepper@redhat.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=mbligh@mbligh.org \
--cc=riel@redhat.com \
/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