public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: "Tvrtko A. Uršulin" <tvrtko.ursulin@zg.htnet.hr>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: MM patches (was Re: why swap at all?)
Date: Mon, 31 May 2004 23:33:43 +1000	[thread overview]
Message-ID: <200405312333.43188.kernel@kolivas.org> (raw)
In-Reply-To: <200405311513.32930.tvrtko.ursulin@zg.htnet.hr>

On Mon, 31 May 2004 23:13, Tvrtko A. Uršulin wrote:
> On Saturday 29 May 2004 10:40, Nick Piggin wrote:
> > It is a cocktail of cleanups, simplification, and enhancements. The
> > main ones that applie here is my split active lists patch (search
> > archives for details), and explicit use-once logic.
>
> I didn't have time to personally test it but just want to share some
> thoughts. This kind of improvement is absolutely necessary for 2.6 to be
> usefull on the desktop. It continues to escape me how come that this kind
> of, almost, bugfix arrives so late during stable period.
>
> Unfortunately it doesn't apply on top of Con's autoregulate swappines (AM
> from now on) which I am currently testing. AM also does an excellent job in
> preventing swap trashing while doing a lot of filesystem reading.
>
> I am curious on how does your patch technically relates to Con's AM, and is
> it possible to merge the two? I know that they do their job on completely
> different ways, so the real question would be: Is there a need for
> something like AM if using your patch, or it completely obsoletes it?

I had a quick look at Nick's patches to see for you and it appears that Nick's 
work completely removes the swappiness dial and introduces a different metric 
called vm_mapped_page_cost which is not interchangeable with the swappiness 
value. ie they cannot work together, sorry.

Con

  reply	other threads:[~2004-05-31 13:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fegqf9v.kmidof@ifi.uio.no>
     [not found] ` <fa.bqpvcrs.u648jq@ifi.uio.no>
2004-05-27 11:39   ` why swap at all? Andy Lutomirski
2004-05-28 21:37     ` Denis Vlasenko
2004-05-28 22:28       ` Bernd Eckenfels
2004-05-29  7:31         ` Denis Vlasenko
2004-05-29  8:40           ` MM patches (was Re: why swap at all?) Nick Piggin
2004-05-29  8:46             ` Nick Piggin
     [not found]             ` <200405292014.23559.matt@lpbproductions.com>
2004-05-30  3:31               ` Nick Piggin
2004-05-31 13:13             ` Tvrtko A. Uršulin
2004-05-31 13:33               ` Con Kolivas [this message]
2004-05-31 17:34             ` Andy Lutomirski
2004-05-31 10:49         ` why swap at all? jlnance
2004-06-01 11:57           ` Lenar Lõhmus
2004-06-01 12:27             ` Robin Rosenberg
2004-06-01 16:49             ` jlnance
2004-06-01 17:38               ` why swap at all? (what the user feels) Martin Olsson
2004-06-01 17:57                 ` Valdis.Kletnieks
2004-06-01 18:01                 ` David Schwartz
2004-06-01 19:01                   ` Robin Rosenberg
2004-06-01 19:04                     ` David Schwartz
2004-06-02 18:38               ` why swap at all? John Hendrikx
2004-06-01 12:21           ` David B. Stevens
2004-05-31 15:48 MM patches (was Re: why swap at all?) Zoltan Boszormenyi

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=200405312333.43188.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tvrtko.ursulin@zg.htnet.hr \
    /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