linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Keith Ansell <keitha@edp.fastfreenet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: bdflush flushing memory mapped pages.
Date: 09 Apr 2003 11:22:43 +0200	[thread overview]
Message-ID: <1049880162.1424.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <007601c2fecd$12209070$230110ac@kaws>

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

On Wed, 2003-04-09 at 21:20, Keith Ansell wrote:
> help
> 
> My application uses SHARED memory mapping files for file I/O, and we have
> observed
> that Linux does not flush dirty pages to disk until munmap or msync are
> called.
> 
> I would like to know are there any development plans which would address
> this issue or
> if there is a version of bdflush which flushes write required pages (dirty
> pages) to disk?

The linux behavior is perfectly fine and conformant to the posix/sus
specifications, applications that break because of this are defective
and need fixing. This is a performance optimisation that the OS is
perfectly allowed to do.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-04-09  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 19:20 bdflush flushing memory mapped pages Keith Ansell
2003-04-09  9:13 ` Andre Hedrick
2003-04-09  9:27   ` Andrew Morton
2003-04-09  9:33     ` Jens Axboe
2003-04-10 20:09     ` Keith Ansell
2003-04-10  8:16       ` Andre Hedrick
2003-04-10  9:02       ` Nick Piggin
2003-04-10 17:04       ` Alan Cox
2003-04-09  9:22 ` Arjan van de Ven [this message]
2003-04-09 10:39 ` Alan Cox

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=1049880162.1424.2.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=keitha@edp.fastfreenet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).