From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Keith Ansell <keitha@edp.fastfreenet.com>
Cc: Andrew Morton <akpm@digeo.com>,
Andre Hedrick <andre@linux-ide.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
axboe@suse.de
Subject: Re: bdflush flushing memory mapped pages.
Date: 10 Apr 2003 18:04:08 +0100 [thread overview]
Message-ID: <1049994246.10869.20.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <01bc01c2ff9d$0dc1aca0$230110ac@kaws>
On Iau, 2003-04-10 at 21:09, Keith Ansell wrote:
> 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 .
Well maybe you should fix the other ports, because they aren't required
to flush that data and you may get burned nastily from it.
Also understand _why_ the policy is the way it is. Flushing mapped files
is bad for performance of the app. Its also useless for most apps
because there are no ordering guarantees implied by it.
If you have a case that needs it all you have to do is fork/clone a
thread which does the needed msync's. If we enforce broken behaviour on
applications they cant fork a thread to stop the msyncs...
next prev parent reply other threads:[~2003-04-10 17: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
2003-04-10 17:04 ` Alan Cox [this message]
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=1049994246.10869.20.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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).