From: Christoph Lameter <clameter@sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 2.6.17-rc1-mm1 3/6] Migrate-on-fault - migrate misplaced page
Date: Tue, 11 Apr 2006 11:32:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604111124090.878@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1144441424.5198.42.camel@localhost.localdomain>
On Fri, 7 Apr 2006, Lee Schermerhorn wrote:
> @@ -184,6 +185,31 @@ int do_migrate_pages(struct mm_struct *m
> int mpol_misplaced(struct page *, struct vm_area_struct *,
> unsigned long, int *);
>
> +#if defined(CONFIG_MIGRATION) && defined(_LINUX_MM_H)
Remove the defined(_LINUX_MM_H). This is pretty obscure.
> Index: linux-2.6.17-rc1-mm1/mm/migrate.c
> ===================================================================
> --- linux-2.6.17-rc1-mm1.orig/mm/migrate.c 2006-04-05 10:14:38.000000000 -0400
> +++ linux-2.6.17-rc1-mm1/mm/migrate.c 2006-04-05 10:14:41.000000000 -0400
> @@ -59,7 +59,8 @@ int isolate_lru_page(struct page *page,
> del_page_from_active_list(zone, page);
> else
> del_page_from_inactive_list(zone, page);
> - list_add_tail(&page->lru, pagelist);
> + if (pagelist)
> + list_add_tail(&page->lru, pagelist);
> }
> spin_unlock_irq(&zone->lru_lock);
> }
isolate lru page can be called without a pagelist now?
> -int fail_migrate_page(struct page *newpage, struct page *page)
> +int fail_migrate_page(struct page *newpage, struct page *page, int faulting)
I do not think the faulting parameter is needed. mapcount == 0 if
we are faulting on an unmapped page. try_to_unmap() will do nothing or
you can check for mapcount.
> *
> * Note that a real pte entry will allow processes that are not
> * waiting on the page lock to use the new page via the page tables
> * before the new page is unlocked.
> */
> - remove_from_swap(newpage);
> + if (!faulting)
> + remove_from_swap(newpage);
> return 0;
If we are faulting then there is nothing to remove. remove_from_swap would
do nothing.
> +out:
> + putback_lru_page(page); /* drops a page ref */
We already have a ref from the fault patch and do not need another one
in isolate_lru page right?
--
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-11 18:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 20:18 [PATCH 2.6.17-rc1-mm1 0/6] Migrate-on-fault - Overview Lee Schermerhorn
2006-04-07 20:22 ` [PATCH 2.6.17-rc1-mm1 1/6] Migrate-on-fault - separate unmap from radix tree replace Lee Schermerhorn
2006-04-11 18:08 ` Christoph Lameter
2006-04-11 18:47 ` Lee Schermerhorn
2006-04-07 20:23 ` [PATCH 2.6.17-rc1-mm1 2/6] Migrate-on-fault - check for misplaced page Lee Schermerhorn
2006-04-11 18:21 ` Christoph Lameter
2006-04-11 19:28 ` Lee Schermerhorn
2006-04-11 19:33 ` Christoph Lameter
2006-04-12 16:43 ` Paul Jackson
2006-04-12 18:49 ` Lee Schermerhorn
2006-04-12 20:55 ` Paul Jackson
2006-04-07 20:23 ` [PATCH 2.6.17-rc1-mm1 3/6] Migrate-on-fault - migrate " Lee Schermerhorn
2006-04-11 18:32 ` Christoph Lameter [this message]
2006-04-11 19:51 ` Lee Schermerhorn
2006-04-07 20:24 ` [PATCH 2.6.17-rc1-mm1 4/6] Migrate-on-fault - handle misplaced anon pages Lee Schermerhorn
2006-04-07 20:26 ` [PATCH 2.6.17-rc1-mm1 5/6] Migrate-on-fault - add MPOL_MF_LAZY Lee Schermerhorn
2006-04-07 20:27 ` [PATCH 2.6.17-rc1-mm1 6/6] Migrate-on-fault - add MPOL_NOOP Lee Schermerhorn
2006-04-09 7:01 ` [PATCH 2.6.17-rc1-mm1 0/6] Migrate-on-fault - Overview Andi Kleen
2006-04-11 18:46 ` Christoph Lameter
2006-04-11 18:52 ` Andi Kleen
2006-04-11 19:03 ` Jack Steiner
2006-04-11 20:40 ` Lee Schermerhorn
2006-04-11 22:12 ` Jack Steiner
2006-04-11 20:40 ` Lee Schermerhorn
2006-04-11 20:40 ` Lee Schermerhorn
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.0604111124090.878@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.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