From: Nikita Danilov <nikita@clusterfs.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Writing out a (file) mmapped page
Date: Tue, 14 Jun 2005 20:37:45 +0400 [thread overview]
Message-ID: <17071.2009.722920.324990@gargle.gargle.HOWL> (raw)
In-Reply-To: <1118763383.16269.61.camel@imp.csi.cam.ac.uk>
Anton Altaparmakov writes:
[...]
>
> That is a little trickier than one might expect because it is partially
> done in hardware (heavily arch dependent though).
>
> When a write to a writable mmapped page happens the CPU sets the page
> dirty flag in hardware. So there is no code where you can see this
> happen. Later on, at msync() time or munmap() time, this hardware dirty
> bit results in a set_page_dirty() being called which for buffer based
This also happens when page migrates to the cold end of "VM LRU list"
(tail of the inactive list, technically).
Nikita.
prev parent reply other threads:[~2005-06-14 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 16:49 Writing out a (file) mmapped page Martin Jambor
2005-06-13 2:32 ` Coywolf Qi Hunt
2005-06-13 6:57 ` Jörn Engel
2005-06-14 15:36 ` Anton Altaparmakov
2005-06-14 16:37 ` Nikita Danilov [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=17071.2009.722920.324990@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).