linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Rik van Riel <riel@redhat.com>, Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] Update Unevictable LRU and Mlocked Pages documentation
Date: Thu, 31 Jul 2008 10:43:49 -0400	[thread overview]
Message-ID: <1217515429.6507.7.camel@lts-notebook> (raw)
In-Reply-To: <4891C8BC.1020509@linux-foundation.org>

On Thu, 2008-07-31 at 09:14 -0500, Christoph Lameter wrote:
> > +Why maintain unevictable pages on an additional LRU list?  Primarily because
> > +we want to be able to migrate unevictable pages between nodes--for memory
> > +deframentation, workload management and memory hotplug.  The linux kernel can
> > +only migrate pages that it can successfully isolate from the lru lists.
> > +Therefore, we want to keep the unevictable pages on an lru-like list, where
> > +they can be found by isolate_lru_page().
> 
> The primary motivation for me was to get rid of the useless scanning
> of pages under memory pressure which led to live lock scenarios.
> mlocked pages are migratable now so the changes do not really change
> anything there. The unevictable lists are also necessary to spill
> pages back to the regular LRUs when unevictable pages become evictable
> again.

Hi, Christoph:

Yes, mlocked pages are migratable now [before the unevictable
lru/mlocked pages patches], but that's because they reside on the LRU
lists.  If we just moved them off to a list that isn't known to
isolate_lru_page(), it wouldn't find them and they wouldn't be migrated.
So, I want to keep them on an LRU-like list so that they remain
migratable.  I was just explaining that rationale in the doc.

Thanks for reviewing,
Lee

--
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:[~2008-07-31 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 21:13 Lee Schermerhorn
2008-07-31 14:14 ` Christoph Lameter
2008-07-31 14:43   ` Lee Schermerhorn [this message]
2008-08-01 13:46     ` Christoph Lameter
2008-08-01 14:06       ` Rik van Riel
2008-08-01 14:16         ` Christoph Lameter
2008-08-01 14:36           ` Lee Schermerhorn
2008-08-01 15:41             ` Christoph Lameter
2008-08-04 20:05 ` Randy Dunlap

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=1217515429.6507.7.camel@lts-notebook \
    --to=lee.schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --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