From: Nick Piggin <nickpiggin@yahoo.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@osdl.org>,
Andrey Savochkin <saw@saw.sw.com.sg>,
linux-kernel@vger.kernel.org
Subject: Re: Q about pagecache data never written to disk
Date: Fri, 10 Sep 2004 03:14:09 +1000 [thread overview]
Message-ID: <41408F61.503@yahoo.com.au> (raw)
In-Reply-To: <20040909172433.GA3106@holomorphy.com>
William Lee Irwin III wrote:
> On Thu, Sep 09, 2004 at 11:32:01PM +1000, Nick Piggin wrote:
>
>>writeback isn't, but the pages will get marked dirty at unmap.
>>But I think I am wrong actually - I don't actually see why the
>>user would have to have the file open.
>
>
> Dirty memory "limits" have no force as applied to mmap() IO, which is
> not a pretty state of affairs with respect to various attempts the VM
> makes at mitigating data structure proliferation associated with dirty
> data.
>
Yeah I know. data structure proliferation and just the simple fact
that it can't immediately be freed is a problem.
What is the alternative? Take a fault every time we write to a clean,
mmapped page?
next prev parent reply other threads:[~2004-09-09 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 8:01 Q about pagecache data never written to disk Andrey Savochkin
2004-09-05 9:22 ` William Lee Irwin III
2004-09-05 10:52 ` Andrew Morton
2004-09-05 11:43 ` Andrey Savochkin
2004-09-05 21:00 ` Andrew Morton
2004-09-06 7:06 ` Andrey Savochkin
2004-09-09 12:39 ` Pavel Machek
2004-09-09 13:15 ` Nick Piggin
2004-09-09 13:37 ` Pavel Machek
2004-09-09 13:32 ` Nick Piggin
2004-09-09 17:24 ` William Lee Irwin III
2004-09-09 17:14 ` Nick Piggin [this message]
2004-09-09 17:35 ` William Lee Irwin III
2004-09-05 16:33 ` William Lee Irwin III
2004-09-06 6:24 ` William Lee Irwin III
2004-09-06 7:02 ` Andrew Morton
2004-09-06 15:12 ` William Lee Irwin III
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=41408F61.503@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=saw@saw.sw.com.sg \
--cc=wli@holomorphy.com \
/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