linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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, 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 15:01:52 -0500	[thread overview]
Message-ID: <20071106150152.3ba1e4cc@bree.surriel.com> (raw)
In-Reply-To: <cfd9edbf0711060241i7ad7e058m3e6795d90c4da82b@mail.gmail.com>

On Tue, 6 Nov 2007 11:41:20 +0100
"Daniel SpAJPYng" <daniel.spang@gmail.com> wrote:

> 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.

I agree.

To get out of the "my patch is better" line of conversation,
I guess you and Marcelo should probably try to figure out
some threshold that you both agree on.

> 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.

Well, if the inactive processes get woken up by the low memory
notification and free some of their memory, the active processes
will use the memory from the inactive ones :)

Not using swap is generally considered a good thing on desktops.

-- 
"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>

  reply	other threads:[~2007-11-06 20:01 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
2007-11-06 20:01       ` Rik van Riel [this message]
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=20071106150152.3ba1e4cc@bree.surriel.com \
    --to=riel@redhat.com \
    --cc=7eggert@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=daniel.spang@gmail.com \
    --cc=drepper@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@kvack.org \
    --cc=mbligh@mbligh.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