From: Martin Maletinsky <maletinsky@scs.ch>
To: kernelnewbies@nl.linux.org, linux-mm@kvack.org
Subject: Meaning of the dirty bit
Date: Thu, 10 Oct 2002 09:46:52 +0200 [thread overview]
Message-ID: <3DA5306C.7B63584@scs.ch> (raw)
Hi,
While studying the follow_page() function (the version of the function that is in place since 2.4.4, i.e. with the write argument), I noticed, that for an address that
should be written to (i.e. write != 0), the function checks not only the writeable flag (with pte_write()), but also the dirty flag (with pte_dirty()) of the page
containing this address.
>From what I thought to understand from general paging theory, the dirty flag of a page is set, when its content in physical memory differs from its backing on the permanent
storage system (file or swap space). Based on this understanding I do not understand why it is necessary to check the dirty flag, in order to ensure that a page is writable
- what am I missing here?
Thanks in advance for any answers
with best regards
Martin Maletinsky
P.S. Pls. put me on cc: in your reply, since I am not on the mailing list.
--
Supercomputing System AG email: maletinsky@scs.ch
Martin Maletinsky phone: +41 (0)1 445 16 05
Technoparkstrasse 1 fax: +41 (0)1 445 16 10
CH-8005 Zurich
--
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/
next reply other threads:[~2002-10-10 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 7:46 Martin Maletinsky [this message]
2002-10-10 8:49 ` Meaning of the dirty bit Dharmender Rai
2002-10-10 8:57 ` Martin Maletinsky
2002-10-10 9:46 ` Dharmender Rai
2002-10-10 11:40 ` Hugh Dickins
2002-10-10 11:55 ` William Lee Irwin III
2002-10-10 13:40 ` Hugh Dickins
2002-10-10 12:11 ` Martin Maletinsky
2002-10-10 13:11 ` Dharmender Rai
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=3DA5306C.7B63584@scs.ch \
--to=maletinsky@scs.ch \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.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 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.