Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 7 Aug 2002 15:34:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 7 Aug 2002 15:34:27 -0400 Received: from pat.uio.no ([129.240.130.16]:19678 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id ; Wed, 7 Aug 2002 15:34:26 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15697.30489.765404.126474@charged.uio.no> Date: Wed, 7 Aug 2002 21:38:01 +0200 To: Gregory Giguashvili Cc: "'trond.myklebust@fys.uio.no'" , "Linux Kernel (E-mail)" Subject: RE: O_SYNC option doesn't work (2.4.18-3) In-Reply-To: References: X-Mailer: VM 7.00 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid Reply-To: trond.myklebust@fys.uio.no From: Trond Myklebust Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1102 Lines: 26 >>>>> " " == Gregory Giguashvili writes: > File locking, meaning lockd? There are so many problems with > file locking in heterogeneous environments that we were moving > towards dropping its usage. Instead, we planned to use some > home grown TCP based lock server mechanism. > I understand that locking file flushes NFS cache, isn't it? Why > can't it be flushed by O_SYNC and "sync" options presence? This > would make the life much easier for programmers... Tough. The above is not part of the O_SYNC spec on any platform and I have no intention of implementing it. The sort of thing you would like to do will be possible with O_DIRECT (which is a design to allow user programs to manage their own caches). That has yet to be integrated into the standard kernel though. 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/