From: "H. Peter Anvin" <hpa@zytor.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 22:30:52 -0700 [thread overview]
Message-ID: <3E9B990C.5000503@zytor.com> (raw)
In-Reply-To: <20030415045637.GB25139@mail.jlokier.co.uk>
Jamie Lokier wrote:
>
> It's a quality of implementation issue if data can remain dirty in RAM
> forever without ever being flushed.
>
> Can this really happen with normal open/mmap/munmap/close usage, or
> does it only occur with long-lived processes like innd which mmap a
> file, dirty the pages but never munmap them?
>
> If the former case does happen, I'd say we're failing on quality of
> implementation. If it's only the latter case, though, fair enough: the
> application writer will have to use msync().
>
The latter, I'm pretty sure. After all, that's what pgflush/bdflush is
all about.
next prev parent reply other threads:[~2003-04-15 5:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:31 Memory mapped files question Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky
2003-04-14 19:53 ` Alan Cox
2003-04-14 21:24 ` Chris Friesen
2003-04-14 20:13 ` Richard B. Johnson
2003-04-14 20:27 ` Frank van Maarseveen
2003-04-14 20:52 ` Richard B. Johnson
2003-04-14 22:08 ` H. Peter Anvin
2003-04-15 4:56 ` Jamie Lokier
2003-04-15 5:30 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:50 Perez-Gonzalez, Inaky
2003-04-14 3:57 Bryan Shumsky
2003-04-14 14:36 ` Martin J. Bligh
2003-04-14 15:07 ` Antonio Vargas
2003-04-14 15:04 ` Martin J. Bligh
2003-04-14 18:07 ` H. Peter Anvin
2003-04-14 20:39 ` Chris Friesen
2003-04-14 21:12 ` H. Peter Anvin
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=3E9B990C.5000503@zytor.com \
--to=hpa@zytor.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.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.