From: Christoph Lameter <clameter@sgi.com>
To: Mel Gorman <mel@skynet.ie>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
Chris Mason <chris.mason@oracle.com>,
reiserfs-devel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: migratepage failures on reiserfs
Date: Mon, 5 Nov 2007 14:46:45 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711051446130.20927@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071105102335.GA6272@skynet.ie>
On Mon, 5 Nov 2007, Mel Gorman wrote:
> The grow_dev_page() pages should be reclaimable even though migration
> is not supported for those pages? They were marked movable as it was
> useful for lumpy reclaim taking back pages for hugepage allocations and
> the like. Would it make sense for memory unremove to attempt migration
> first and reclaim second?
Note that a page is still movable even if there is no file system method
for migration available. In that case the page needs to be cleaned before
it can be moved.
--
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-05 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 18:27 migratepage failures on reiserfs Badari Pulavarty
2007-10-30 17:54 ` Chris Mason
2007-10-30 21:54 ` Badari Pulavarty
2007-10-30 22:58 ` Chris Mason
2007-10-30 23:08 ` Badari
2007-10-31 0:05 ` Zan Lynx
2007-10-31 16:14 ` Badari Pulavarty
2007-10-31 17:40 ` Chris Mason
2007-11-01 16:38 ` Badari Pulavarty
2007-11-01 15:51 ` Chris Mason
2007-11-01 18:10 ` Badari Pulavarty
2007-11-02 16:46 ` Badari Pulavarty
2007-11-05 10:23 ` Mel Gorman
2007-11-05 13:40 ` Chris Mason
2007-11-05 22:46 ` Christoph Lameter [this message]
2007-11-07 14:56 ` Mel Gorman
2007-11-07 15:58 ` Badari Pulavarty
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=Pine.LNX.4.64.0711051446130.20927@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=pbadari@us.ibm.com \
--cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).