From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 2.6.17-rc1-mm3] add migratepage addresss space op to shmem
Date: Tue, 25 Apr 2006 11:58:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0604251153300.29020@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604241447520.8904@schroedinger.engr.sgi.com>
On Mon, 24 Apr 2006, Christoph Lameter wrote:
> On Mon, 24 Apr 2006, Hugh Dickins wrote:
> >
> > While that's not wrong, wouldn't the right fix be something else?
>
> His patch avoids going through the fallback functions and allows
> migrating dirty shmem pages without pageout. That is good.
True.
> Index: linux-2.6/mm/migrate.c
> ===================================================================
> --- linux-2.6.orig/mm/migrate.c 2006-04-18 12:51:31.000000000 -0700
> +++ linux-2.6/mm/migrate.c 2006-04-24 15:03:10.000000000 -0700
> @@ -439,6 +439,11 @@ redo:
> goto unlock_both;
> }
>
> + if (try_to_unmap(page, 1) == SWAP_FAIL) {
> + rc = -EPERM;
> + goto unlock_both;
> + }
> +
> /*
> * Default handling if a filesystem does not provide
> * a migration function. We can only migrate clean
Perhaps. But there seem to be altogether too many ways through this
code: this part of migrate_pages then starts to look rather like,
but not exactly like, swap_page. Feels like it needs refactoring.
Hugh
--
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:[~2006-04-25 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 20:08 Hugh Dickins
2006-04-24 22:04 ` Christoph Lameter
2006-04-25 10:58 ` Hugh Dickins [this message]
2006-04-25 16:09 ` Christoph Lameter
2006-04-27 23:05 ` Christoph Lameter
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.0604251153300.29020@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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