Re: bdflush flushing memory mapped pages.

[Alan Cox]

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...