From: Peter Zijlstra <peterz@infradead.org>
To: xue yong <ultraice.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm: dirty page problem
Date: Tue, 23 Jun 2009 12:33:39 +0200 [thread overview]
Message-ID: <1245753219.19816.1586.camel@twins> (raw)
In-Reply-To: <fc71709d0906230202w14da8ffdpf457f7a6ed658a28@mail.gmail.com>
On Tue, 2009-06-23 at 17:02 +0800, xue yong wrote:
> I did some search in the changlogs between 2..6.16 adn 2.6.19.
> I found this in http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.19
>
> and I concluded that the kernel below 2.6.19 can't tracking shared
> dirty pages, am I right?
>
> commit edc79b2a46ed854595e40edcf3f8b37f9f14aa3f
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Mon Sep 25 23:30:58 2006 -0700
>
> [PATCH] mm: balance dirty pages
> commit d08b3851da41d0ee60851f2c75b118e1f7a5fc89
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Mon Sep 25 23:30:57 2006 -0700
>
> [PATCH] mm: tracking shared dirty pages
Correct, prior to .19 we didn't have effective tracking of dirty pages.
munmap() and msync() would walk the page tables and collect dirty pages,
but without explicit action these pages would stay hidden.
These patches you found change that by mapping clean shared pages RO and
taking a fault on the dirtying write. We once again map then RO when
they'd be written out to disk.
next prev parent reply other threads:[~2009-06-23 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 8:17 mm: dirty page problem xue yong
2009-06-23 9:02 ` xue yong
2009-06-23 10:33 ` Peter Zijlstra [this message]
[not found] ` <fc71709d0906230443pf8c4b34pcd4b7fa798fbf1ed@mail.gmail.com>
[not found] ` <1245757970.19816.1675.camel@twins>
2009-06-23 13:32 ` xue yong
2009-06-23 13:38 ` Peter Zijlstra
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=1245753219.19816.1586.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ultraice.kernel@gmail.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