linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Martin Schwidefsky <schwidefsky@googlemail.com>
Cc: Rik van Riel <riel@redhat.com>, linux-mm <linux-mm@kvack.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: inactive-clean list
Date: Wed, 26 Jul 2006 13:11:08 +0200	[thread overview]
Message-ID: <1153912268.2732.30.camel@taijtu> (raw)
In-Reply-To: <6e0cfd1d0607260400r731489a1tfd9e6c5a197fb0bd@mail.gmail.com>

On Wed, 2006-07-26 at 13:00 +0200, Martin Schwidefsky wrote:
> On 7/23/06, Rik van Riel <riel@redhat.com> wrote:
> > Peter Zijlstra wrote:
> > > This patch implements the inactive_clean list spoken of during the VM summit.
> > > The LRU tail pages will be unmapped and ready to free, but not freeed.
> > > This gives reclaim an extra chance.
> >
> > This patch makes it possible to implement Martin Schwidefsky's
> > hypervisor-based fast page reclaiming for architectures without
> > millicode - ie. Xen, UML and all other non-s390 architectures.
> 
> Hmm, I wonder how the inactive clean list helps in regard to the fast
> host reclaim
> scheme. In particular since the memory pressure that triggers the
> reclaim is in the
> host, not in the guest. So all pages might be on the active list but
> the host still
> wants to be able to discard pages.
> 

I think Rik would want to set all the already unmapped pages to volatile
state in the hypervisor.

These pages can be dropped without loss of information on the guest
system since they are all already on a backing-store, be it regular
files or swap.



--
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:[~2006-07-26 11:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 20:24 Peter Zijlstra
2006-07-18  3:37 ` Christoph Lameter
2006-07-18 12:16   ` Peter Zijlstra
2006-07-18 13:29     ` Christoph Lameter
2006-07-18 13:55       ` Martin J. Bligh
2006-07-18 13:59         ` Christoph Lameter
2006-07-18 15:12           ` Martin J. Bligh
2006-07-18 15:57             ` Christoph Lameter
2006-07-18 16:23               ` Martin J. Bligh
2006-07-18 14:03         ` Christoph Lameter
2006-07-18 14:25           ` Andrew Morton
2006-07-18 14:45             ` Christoph Lameter
2006-07-18 15:59               ` KAMEZAWA Hiroyuki
2006-07-23  5:50 ` Rik van Riel
2006-07-24 18:11   ` Christoph Lameter
2006-07-24 19:00     ` Rik van Riel
2006-07-25 20:25       ` Christoph Lameter
2006-07-25 21:37         ` Rik van Riel
2006-07-25 23:03           ` Christoph Lameter
2006-07-26  0:02             ` Rik van Riel
2006-07-26  0:05               ` Christoph Lameter
2006-07-26 11:00   ` Martin Schwidefsky
2006-07-26 11:11     ` Peter Zijlstra [this message]
2006-07-26 13:04       ` Martin Schwidefsky
2006-07-26 14:45         ` Peter Zijlstra
2006-07-27 11:16           ` Martin Schwidefsky
2006-07-26 15:41         ` Rik van Riel

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=1153912268.2732.30.camel@taijtu \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=schwidefsky@googlemail.com \
    --cc=torvalds@osdl.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