From: Martin Maletinsky <maletinsky@scs.ch>
To: linux-mm@kvack.org, kernelnewbies@nl.linux.org
Subject: Question on set_page_dirty()
Date: Tue, 10 Dec 2002 10:59:34 +0100 [thread overview]
Message-ID: <3DF5BB06.A6F6AFFD@scs.ch> (raw)
Hello,
Looking at the function set_page_dirty() (in linux 2.4.18-3 - see below) I noticed, that it not only sets the pages PG_dirty bit (as the SetPageDirty() macro does), but
additionnally may link the page onto a queue (more precisely the dirty queue of it's 'mapping').
What is the meaning of this dirty queue, what is the effect of linking a page onto that queue, and when should the set_page_dirty() function be used rather than the
SetPageDirty() macro?
Thanks in advance for any help
with best regards
Martin Maletinsky
P.S. Please put me on CC: in your reply, since I am not in the mailing list.
*
153 * Add a page to the dirty page list.
154 */
155 void set_page_dirty(struct page *page)
156 {
157 if (!test_and_set_bit(PG_dirty, &page->flags)) {
158 struct address_space *mapping = page->mapping;
159
160 if (mapping) {
161 spin_lock(&pagecache_lock);
162 list_del(&page->list);
163 list_add(&page->list, &mapping->dirty_pages);
164 spin_unlock(&pagecache_lock);
165
166 if (mapping->host)
167 mark_inode_dirty_pages(mapping->host);
168 }
169 }
170 }
--
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-12-10 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 9:59 Martin Maletinsky [this message]
2002-12-11 8:01 ` Jan Hudec
2002-12-12 9:29 ` Ingo Oeser
2002-12-12 12:42 ` Stephen C. Tweedie
2002-12-12 18:20 ` Andrew Morton
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=3DF5BB06.A6F6AFFD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox