From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wedgwood Subject: Re: [RFC] [PATCH] Relative lazy atime Date: Sat, 5 Aug 2006 11:36:09 -0700 Message-ID: <20060805183609.GA7564@tuatara.stupidest.org> References: <20060803063622.GB8631@goober> <20060805122537.GA23239@lst.de> <1154797123.12108.6.camel@kleikamp.austin.ibm.com> <1154797475.3054.79.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Kleikamp , Christoph Hellwig , Valerie Henson , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Akkana Peck , Mark Fasheh , Jesse Barnes , jsipek@cs.sunysb.edu, Al Viro Return-path: Received: from smtp109.sbc.mail.mud.yahoo.com ([68.142.198.208]:4476 "HELO smtp109.sbc.mail.mud.yahoo.com") by vger.kernel.org with SMTP id S1751464AbWHESgR (ORCPT ); Sat, 5 Aug 2006 14:36:17 -0400 To: Arjan van de Ven Content-Disposition: inline In-Reply-To: <1154797475.3054.79.camel@laptopd505.fenrus.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Aug 05, 2006 at 07:04:34PM +0200, Arjan van de Ven wrote: > the vfs shouldn't consider it clean, it should consider it > "atime-only dirty".. with that many of the vfs interaction issues > ought to go away should it be atime-dirty or non-critical-dirty? (ie. make it more generic to cover cases where we might have other non-critical fields to flush if we can but can tolerate loss if we dont) adminitedly atime is the only one i can think of now