From: Ray Bryant <raybry@engr.sgi.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
Dave Hansen <haveblue@us.ibm.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: question on page-migration code
Date: Mon, 11 Apr 2005 14:00:02 -0500 [thread overview]
Message-ID: <425AC932.2030300@engr.sgi.com> (raw)
In-Reply-To: <20050407180858.GB19449@logos.cnet>
Marcelo Tosatti wrote:
> Who is using the page?
>
> A little debugging might help similar to what bad_page does can help:
>
> printk(KERN_EMERG "flags:0x%0*lx mapping:%p mapcount:%d count:%d\n",
> (int)(2*sizeof(page_flags_t)), (unsigned long)page->flags,
> page->mapping, page_mapcount(page), page_count(page));
> --
Marcello,
I wrote:
"PagePrivate() is cleared by truncation specific code in migrate_onepage(),
but it doesn't appear to be cleared (directly) by code on the
generic_migrate_page() patch. I wonder if this has something to do with
the problem I am seeing. "
Ooops. I didn't look deep enough. migrate_page_common() calls
writeback_and_free_buffers(), which in turn calls try_to_release_page()
which will eventually call down to __clear_page_buffers() which will
clear PagePrivate().
So it looks like the following is perhaps what is happening:
(1) We come into migrate_one_page() with the pages dirty. (The first
time we enter the -EAGAIN section of migate_page_common() we have
flags = 105d, the last time through before succeeding, flags are
104d, and when we do return flags=004d.
(2) We have to wait around until the pages get paged out before we can
migrated them. (flags=004d).
I'll have to check and see if I believe it might take 3 minutes to page
out all of the pages of my application. If so, then this explains what
is happening.
Does that make sense?
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-04-11 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 22:16 question on page-migration code Ray Bryant
2005-04-07 18:08 ` Marcelo Tosatti
2005-04-11 14:20 ` Ray Bryant
2005-04-11 18:31 ` Ray Bryant
2005-04-11 23:41 ` Hirokazu Takahashi
2005-04-12 4:57 ` Ray Bryant
2005-04-12 5:43 ` Ray Bryant
2005-04-13 2:30 ` IWAMOTO Toshihiro
2005-04-13 4:43 ` Hirokazu Takahashi
2005-04-15 6:41 ` IWAMOTO Toshihiro
2005-04-15 12:53 ` Marcelo Tosatti
2005-04-18 10:37 ` IWAMOTO Toshihiro
2005-04-12 16:46 ` Dave Hansen
2005-04-13 10:48 ` Hirokazu Takahashi
2005-04-14 15:57 ` Marcelo Tosatti
2005-04-19 2:46 ` Ray Bryant
2005-04-20 18:16 ` Marcelo Tosatti
2005-04-12 19:29 ` Ray Bryant
2005-04-11 19:00 ` Ray Bryant [this message]
2005-04-11 19:59 ` Ray Bryant
2005-04-07 22:44 ` Ray Bryant
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 23:05 Ray Bryant
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=425AC932.2030300@engr.sgi.com \
--to=raybry@engr.sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=taka@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.