Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Aug 2002 09:39:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Aug 2002 09:39:23 -0400 Received: from mons.uio.no ([129.240.130.14]:50110 "EHLO mons.uio.no") by vger.kernel.org with ESMTP id ; Thu, 8 Aug 2002 09:39:22 -0400 To: Gregory Giguashvili Cc: "'Jesse Pollard'" , "Linux Kernel (E-mail)" Subject: Re: O_SYNC option doesn't work (2.4.18-3) References: From: Trond Myklebust Date: 08 Aug 2002 15:42:30 +0200 In-Reply-To: Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1035 Lines: 19 >>>>> " " == Gregory Giguashvili writes: > When the writer closes the file, how do you make the readers > see the latest changes (assuming that you always open/close > files per transaction type). There is a convention amongst NFS clients that each client will always flush *all* changes to the server upon close(), and it will always check the file attributes upon a call to open() (and if the mtime or file size have changed, one flushes the page cache). This suffices to guarantee file cache consistency *provided* that only one client opens the file at any given time. If locking is used, all changes are flushed to the server upon taking/releasing a lock, and the page cache is guaranteed to get flushed upon taking a lock. Cheers, Trond - 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/