From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [PATCH] writeback: reset inode dirty time when adding it back to empty s_dirty list Date: Wed, 25 Mar 2009 16:07:02 -0400 Message-ID: <1238011622.5676.3.camel@think.oraclecorp.com> References: <1237840233-11045-1-git-send-email-jlayton@redhat.com> <20090324135720.GA25314@localhost> <20090324102806.4f38fd26@tleilax.poochiereds.net> <20090324104657.6907b19e@tleilax.poochiereds.net> <20090325012829.GA7506@localhost> <20090324221528.2bb7c50b@tleilax.poochiereds.net> <20090325025037.GA17374@localhost> <20090325075110.028f0d1d@tleilax.poochiereds.net> <20090325121742.GA22869@localhost> <20090325165500.GA6047@infradead.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Wu Fengguang , Jeff Layton , Ian Kent , Dave Chinner , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org" , "akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org" , "linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: "hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org" Return-path: In-Reply-To: <20090325165500.GA6047-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 2009-03-25 at 12:55 -0400, hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org wrote: > On Wed, Mar 25, 2009 at 08:17:43PM +0800, Wu Fengguang wrote: > > Now there are now two possible solutions: > > - unconditionally update dirtied_when in redirty_tail(); > > - keep dirtied_when and redirty inodes to a new dedicated queue. > > The first one involves less code, the second one allows more flexible timing. > > > > NFS/XFS could be a good starting point for discussing the > > requirements, so that we can reach a suitable solution. > > Note that the XFS requirement also applies to all filesystems that > perform some sort of metadata updats on I/O completeion. That includes > at least ext4, btrfs and most likely the cluster filesystems too. btrfs at least doesn't dirty the inode on I/O completion. It just puts the changes directly into the btree blocks. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html