From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263986AbTDNV5Y (for ); Mon, 14 Apr 2003 17:57:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263996AbTDNV5Y (for ); Mon, 14 Apr 2003 17:57:24 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:50443 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S263986AbTDNV5U (for ); Mon, 14 Apr 2003 17:57:20 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: Memory mapped files question Date: 14 Apr 2003 15:08:48 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: <004301c302bd$ed548680$fe64a8c0@webserver> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: <004301c302bd$ed548680$fe64a8c0@webserver> By author: "Bryan Shumsky" 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 -- at work, 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