From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 0D4907F4E for ; Thu, 27 Nov 2014 09:28:48 -0600 (CST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay1.corp.sgi.com (Postfix) with ESMTP id CF5EB8F8052 for ; Thu, 27 Nov 2014 07:28:47 -0800 (PST) Received: from bombadil.infradead.org ([198.137.202.9]) by cuda.sgi.com with ESMTP id ANaJIZ2OD3CaPHPT (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 27 Nov 2014 07:28:46 -0800 (PST) Date: Thu, 27 Nov 2014 07:28:46 -0800 From: Christoph Hellwig Subject: Re: [PATCH-v4 1/7] vfs: split update_time() into update_time() and write_time() Message-ID: <20141127152846.GA24779@infradead.org> References: <1416997437-26092-1-git-send-email-tytso@mit.edu> <1416997437-26092-2-git-send-email-tytso@mit.edu> <20141126192328.GA20436@infradead.org> <20141127144116.GA14091@thunk.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20141127144116.GA14091@thunk.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Theodore Ts'o Cc: Christoph Hellwig , Linux Filesystem Development List , Ext4 Developers List , Linux btrfs Developers List , XFS Developers FYI, I suspect for now the best might be to let filesystems that define ->update_times work as-is and not tie them into the infrastructure. At least for XFS I suspect the lazy updates might better be handled internally, although I'm not entirely sure yet. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs