Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 3 Sep 2002 12:29:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 3 Sep 2002 12:29:05 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:53263 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Tue, 3 Sep 2002 12:29:03 -0400 Date: Tue, 3 Sep 2002 13:33:20 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@duckman.distro.conectiva To: "Peter T. Breuer" Cc: root@chaos.analogic.com, linux kernel Subject: Re: [RFC] mount flag "direct" (fwd) In-Reply-To: <200209031629.g83GT2e08075@oboe.it.uc3m.es> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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: 1350 Lines: 35 On Tue, 3 Sep 2002, Peter T. Breuer wrote: > > How does the other user's of this device "know" that there is > > a new file so it can update its notion of the block-device state? > > The block device itself is stateless at the block level. Every block > access goes "direct to the metal". > > The question is how much FS state is cached on either kernel. > If it is too much, then I will ask how I can cause to be less, perhaps > by use of a flag that parallels how O_DIRECT works. I thought that new > files were entries in a directories inode and I agree that inodes are > held in memory! But I don't know when they are first read or reread. And neither can you know. After all, this is filesystem dependant. You cannot decide whether filesystem-independant clustering is possible unless you know that all the filesystems play by your rules. So much for filesystem-independance. regards, Rik -- http://www.linuxsymposium.org/2002/ "You're one of those condescending OLS attendants" "Here's a nickle kid. Go buy yourself a real t-shirt" http://www.surriel.com/ http://distro.conectiva.com/ - 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/