From: Anand Eswaran <aeswaran@andrew.cmu.edu>
To: linux-mm@kvack.org
Cc: aeswaran@ece.cmu.edu
Subject: Desperate plea
Date: Fri, 27 Feb 2004 21:11:13 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58-035.0402272032450.3342@unix49.andrew.cmu.edu> (raw)
Hi :
Sorry but kernelnewbies seems offline, you're the only source
that can help me !
Pls be kind enough to respond OR if busy, pls point me out to
some source which answers the question.
Question
--------
I'm observing the following execution path in page_launder_zone
handling *anonymous* page in 2.4.18:
1) A page starts out with PageInactiveDirty(page) and page->pte_chain ON
2) After add_to_swap() , PageInactiveDirty(page), page->pte_chain, page->mapping and
PageSwapCache(page) are ON
3) After try_to_unmap(), page->mapping is turned OFF
4) After that, it enters the writepage() function, after which it results
in non-NULL page->buffers
5) kswapd then continues to the next page.
Q1 :
---
When do these buffers formed from anonymous pages
in step 4 get written out to disk? I thought writepage was supposed to
clean the page's buffers, so Im surprised that after the writepage()
page->buffers is non-null.
Q2:
---
Also, if anonymous pages always result in non-NULL buffers (as in step 4
), in the launder loop:
if (page->buffers) {
page_cache_get(page);
spin_unlock(&pagemap_lru_lock);
if (try_to_release_page(page,gfp_mask)) {
if (!page->mapping) {
...
why is there the need for the "if (!page->mapping)" loop?
Seems like by this stage, anonymous pages already are mapped
to swap_cache?
I know Im missing something. Could someone pls point it out to me?
Thanks a lot!
-----
Anand.
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2004-02-28 2:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.58-035.0402272032450.3342@unix49.andrew.cmu.edu \
--to=aeswaran@andrew.cmu.edu \
--cc=aeswaran@ece.cmu.edu \
--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