From: Carsten Otte <cotte.de@gmail.com>
To: Mauricio Lin <mauriciolin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to identify cow (copy-on-write) pages during kernel execution?
Date: Mon, 20 Jun 2005 13:35:33 +0200 [thread overview]
Message-ID: <5c77e7070506200435229cd064@mail.gmail.com> (raw)
In-Reply-To: <3f250c71050620043066ff0262@mail.gmail.com>
On 6/20/05, Mauricio Lin <mauriciolin@gmail.com> wrote:
> So the only way to identify copy-on-write pages is when page fault
> related to copy-on-write happens, right? I mean in the
> handle_pte_fault() that calls do_wp_page().
That shows you at the time of copy, and at a given time later you can
also walk the mm and look that the pte's to see if they are writable.
prev parent reply other threads:[~2005-06-20 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 5:45 How to identify cow (copy-on-write) pages during kernel execution? Mauricio Lin
2005-06-20 6:33 ` Nick Piggin
2005-06-20 11:09 ` Carsten Otte
2005-06-20 11:30 ` Mauricio Lin
2005-06-20 11:35 ` Carsten Otte [this message]
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=5c77e7070506200435229cd064@mail.gmail.com \
--to=cotte.de@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mauriciolin@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 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.