From: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>,
Hirokazu Takahashi <taka@valinux.co.jp>,
haveblue@us.ibm.com, raybry@engr.sgi.com, linux-mm@kvack.org
Subject: Re: question on page-migration code
Date: Mon, 18 Apr 2005 19:37:35 +0900 [thread overview]
Message-ID: <20050418103735.2BB3C7046D@sv1.valinux.co.jp> (raw)
In-Reply-To: <20050415125355.GA19190@logos.cnet>
Hi,
At Fri, 15 Apr 2005 09:53:55 -0300,
Marcelo Tosatti wrote:
> On Fri, Apr 15, 2005 at 03:41:38PM +0900, IWAMOTO Toshihiro wrote:
> > At Thu, 14 Apr 2005 12:57:34 -0300,
> > Marcelo Tosatti wrote:
> > > That said, I see no need to reset PG_dirty in case it was not set before
> > > migration, as you propose.
> >
> > I think PG_dirty should be reset, as the side effect is probably
> > unacceptable for Ray's application. It would be a bit more
> > complicated than just changing page and PTE bits, but I think it's
> > doable.
>
> Yes, makes sense.
>
> Question: Who is causing the writeouts here?
>
> Is there memory pressure or is it pdflush?
>
> Its not the migration code? (that would be a problem I think).
If I understand correctly, writebacks happen in the following way.
1. The migration code unmaps dirty PTEs.
2. try_to_unmap() calls set_page_dirty() for such pages, setting
PG_dirty and the dirty radix tree tag.
3. When pdflush is woken, it calls do_writepages().
4. At least for ext2 (I assume it is true for most file systems),
do_writepage() calls result in mpage_writepages() calls, which scan
radix trees for dirty tags.
--
IWAMOTO Toshihiro
--
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-18 10:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 22:16 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 [this message]
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
2005-04-11 19:59 ` Ray Bryant
2005-04-07 22:44 ` Ray Bryant
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=20050418103735.2BB3C7046D@sv1.valinux.co.jp \
--to=iwamoto@valinux.co.jp \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=raybry@engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox