From: Mel Gorman <mel@csn.ul.ie>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, y-goto@jp.fujitsu.com, hugh@veritas.com
Subject: Re: [RFC] memory unplug v5 [1/6] migration by kernel
Date: Thu, 14 Jun 2007 19:04:16 +0100 [thread overview]
Message-ID: <46718320.1010500@csn.ul.ie> (raw)
In-Reply-To: <20070615011536.beaa79c1.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> On Thu, 14 Jun 2007 09:12:37 -0700 (PDT)
> Christoph Lameter <clameter@sgi.com> wrote:
>
>>> An unmapped swapcache page, which is just added to LRU, may be accessed via migrate_page().
>>> But page->mapping is NULL yet.
>> Yes then lets add a check for page->mapping == NULL there.
>>
>> if (!page->mapping)
>> goto unlock;
>>
>> That will retry the migration on the next pass. Add some concise comment
>> explaining the situation. This is general bug in page migration.
>>
> Ok, will do. thank you for your advice.
>
I am currently testing what I believe your patches currently look like.
In combination with the isolate lru page fix patch, things are looking
better than they were. Previously I had seen some very bizarre errors
when migrating due to compaction of memory but I'm not seeing them now.
I hadn't been reporting because it was difficult to tell if migration
was at fault or what memory compaction was doing.
--
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-06-14 18:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 6:56 [RFC] memory unplug v5 [0/6] intro KAMEZAWA Hiroyuki
2007-06-14 6:59 ` [RFC] memory unplug v5 [1/6] migration by kernel KAMEZAWA Hiroyuki
2007-06-14 7:01 ` Christoph Lameter
2007-06-14 7:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:22 ` Christoph Lameter
2007-06-14 7:41 ` KAMEZAWA Hiroyuki
2007-06-14 7:47 ` Christoph Lameter
2007-06-14 8:29 ` KAMEZAWA Hiroyuki
2007-06-14 14:19 ` Christoph Lameter
2007-06-14 16:02 ` KAMEZAWA Hiroyuki
2007-06-14 16:12 ` Christoph Lameter
2007-06-14 16:15 ` KAMEZAWA Hiroyuki
2007-06-14 18:04 ` Mel Gorman [this message]
2007-06-14 22:31 ` KAMEZAWA Hiroyuki
2007-06-15 9:43 ` KAMEZAWA Hiroyuki
2007-06-15 9:53 ` KAMEZAWA Hiroyuki
2007-06-15 14:41 ` Christoph Lameter
2007-06-15 15:36 ` KAMEZAWA Hiroyuki
2007-06-14 7:00 ` [RFC] memory unplug v5 [2/6] isolate lru page race fix KAMEZAWA Hiroyuki
2007-06-14 7:01 ` [RFC] memory unplug v5 [3/6] walk memory resources assist function KAMEZAWA Hiroyuki
2007-06-15 6:05 ` David Rientjes
2007-06-15 6:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:03 ` [RFC] memory unplug v5 [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-15 15:46 ` Dave Hansen
2007-06-15 16:59 ` KAMEZAWA Hiroyuki
2007-06-14 7:04 ` [RFC] memory unplug v5 [5/6] page unplug KAMEZAWA Hiroyuki
2007-06-15 6:04 ` David Rientjes
2007-06-15 6:12 ` KAMEZAWA Hiroyuki
2007-06-15 14:35 ` Christoph Lameter
2007-06-15 14:40 ` Andy Whitcroft
2007-06-15 15:52 ` Dave Hansen
2007-06-15 17:03 ` KAMEZAWA Hiroyuki
2007-06-15 21:09 ` Dave Hansen
2007-06-14 7:06 ` [RFC] memory unplug v5 [6/6] ia64 interface KAMEZAWA Hiroyuki
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=46718320.1010500@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=y-goto@jp.fujitsu.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