From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sage Weil Subject: Re: [PATCH RFC] vfs: add a O_NOMTIME flag Date: Mon, 11 May 2015 09:24:09 -0700 (PDT) Message-ID: References: <1430949612-21356-1-git-send-email-zab@redhat.com> <20150507002617.GJ4327@dastard> <20150507172053.GA659@lenny.home.zabbo.net> <20150508221325.GM4327@dastard> <20150511144719.GA14088@thunk.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Trond Myklebust , Dave Chinner , Zach Brown , Alexander Viro , Linux FS-devel Mailing List , Linux Kernel Mailing List , Linux API Mailing List To: Theodore Ts'o Return-path: In-Reply-To: <20150511144719.GA14088-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 11 May 2015, Theodore Ts'o wrote: > On Sun, May 10, 2015 at 07:13:24PM -0400, Trond Myklebust wrote: > > That makes it completely non-generic though. By putting this in the > > VFS, you are giving applications a loaded gun that is pointed straight > > at the application user's head. > > Let me re-ask the question that I asked last week (and was apparently > ignored). Why not trying to use the lazytime feature instead of > pointing a head straight at the application's --- and system > administrators' --- heads? Sorry Ted, I thought I responded already. The goal is to avoid inode writeout entirely when we can, and as I understand it lazytime will still force writeout before the inode is dropped from the cache. In systems like Ceph in particular, the IOs can be spread across lots of files, so simply deferring writeout doesn't always help. sage