Re: Memory mapped files question

[H. Peter Anvin]

Followup to:  <004301c302bd$ed548680$fe64a8c0@webserver>
By author:    "Bryan Shumsky" <[e-mail]>
In newsgroup: linux.dev.kernel
>
> Hi, everyone.  Thanks for all your responses.  Our confusion is that in Unix
> environments, when we modify memory in memory-mapped files the underlying
> system flusher manages to flush the files for us before the files are
> munmap'ed or msysnc'ed.
> 

Bullshit.  It might work on one particular Unix implementation, but
the definition of Unix, the Single Unix Standard, does explicitly
*not* require this behavior.

> Rewriting all of our code to manually handle the flushing is a MAJOR
> undertaking, so I was hoping there might be some sneaky solution you could
> come up with.  Any ideas?

Your code is fundamentally broken.  You need to fix it.

	-hpa

-- 
<[e-mail]> at work, <[e-mail]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64