From: Andrew Crawford <acrawford@ieee.org>
To: linux-mm@kvack.org
Subject: Re: The long, long life of an inactive_dirty page
Date: Wed, 12 May 2004 08:28:41 -0700 (PDT) [thread overview]
Message-ID: <200405121528.i4CFSfOn057287@newsguy.com> (raw)
Arjan van de Ven wrote:
>bdflush and co WILL commit the data to disk after like 30 seconds.
>They will not move it to inactive_clean; that will happen at the first
>sight of memory pressure. The code that does that notices that the data
>isn't dirty and won't do a write-out just a move.
Thanks for that. I have a couple of follow-up questions if I may be so bold:
1. Is there any way, from user space, to distinguish inactive_dirty pages
which have actually been written from those which haven't?
2. Is there any reason, conceptually, that bdflush shouldn't move the pages to
the inactive_clean list as page_launder does? After all, they become "known
clean" at that point, not X hours later when there is a memory shortfall.
Cheers,
Andrew
--
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>
next reply other threads:[~2004-05-12 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 15:28 Andrew Crawford [this message]
2004-05-12 16:29 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2004-05-12 19:18 Andrew Crawford
2004-05-12 18:24 Andrew Crawford
2004-05-12 18:46 ` Arjan van de Ven
2004-05-12 14:11 Andrew Crawford
2004-05-12 14:51 ` Arjan van de Ven
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=200405121528.i4CFSfOn057287@newsguy.com \
--to=acrawford@ieee.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