From: Nick Piggin <piggin@cyberone.com.au>
To: Keith Ansell <keitha@edp.fastfreenet.com>
Cc: Andrew Morton <akpm@digeo.com>,
Andre Hedrick <andre@linux-ide.org>,
linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: bdflush flushing memory mapped pages.
Date: Thu, 10 Apr 2003 19:02:15 +1000 [thread overview]
Message-ID: <3E953317.1090406@cyberone.com.au> (raw)
In-Reply-To: <01bc01c2ff9d$0dc1aca0$230110ac@kaws>
Keith Ansell wrote:
>Thank you for your prompt replies.
>
>I realise that Linux conforms to the letter of the specification, but maybe
>not the spirit of the it.
>
>I am porting a Database solution to Linux from Unix SVR4, Sco OpenServer and
>AIX, where all write required memory mapped files are flushed to disk with
>the system flusher, my users have large systems (some in excess of 600
>concurrent connections) flushing memory mapped files is a big part of are
>systems performance. This ensures that in the event of a catastrophic
>system failure the customers vitual business data has been written to disk .
>
As Andrew mentioned, msync would do what you want. It seems
to me though, that your database solution wants a stronger
guarantee about the safety of the data than asynchronous
writes will provide anyway.
next prev parent reply other threads:[~2003-04-10 8:51 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 [this message]
2003-04-10 17:04 ` Alan Cox
2003-04-09 9:22 ` Arjan van de Ven
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=3E953317.1090406@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@digeo.com \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--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).