From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [RFC] [PATCH] Relative lazy atime Date: Sat, 05 Aug 2006 06:22:50 -0700 Message-ID: <44D49BAA.6050501@linux.intel.com> References: <20060803063622.GB8631@goober> <20060805122537.GA23239@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Valerie Henson , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Akkana Peck , Mark Fasheh , Jesse Barnes , Chris Wedgwood , jsipek@cs.sunysb.edu, Al Viro Return-path: Received: from mga07.intel.com ([143.182.124.22]:12713 "EHLO azsmga101.ch.intel.com") by vger.kernel.org with ESMTP id S1161312AbWHENXH (ORCPT ); Sat, 5 Aug 2006 09:23:07 -0400 To: Christoph Hellwig In-Reply-To: <20060805122537.GA23239@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Christoph Hellwig wrote: > Another idea, similar to how atime updates work in xfs currently might > be interesting: Always update atime in core, but don't start a > transaction just for it - instead only flush it when you'd do it anyway, > that is another transaction or evicting the inode. this is sort of having a "dirty" and "dirty atime" split for the inode I suppose.. shouldn't be impossible to do with a bit of vfs support..