Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Memory mapped files question | Date | 14 Apr 2003 15:08:48 -0700 |
| |
Followup to: <004301c302bd$ed548680$fe64a8c0@webserver> By author: "Bryan Shumsky" <bzs@via.com> 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
-- <hpa@transmeta.com> at work, <hpa@zytor.com> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |