From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: vm/fs meetup details Date: Fri, 6 Jul 2007 12:26:23 +0200 Message-ID: <20070706102623.GA846@lazybastard.org> References: <20070705040138.GG32240@wotan.suse.de> <468D303E.4040902@redhat.com> <137D15F6-EABE-4EC1-A3AF-DAB0A22CF4E3@oracle.com> <20070705212757.GB12413810@sgi.com> <468D6569.6050606@redhat.com> <20070706022651.GG14215@wotan.suse.de> <20070706100110.GD12413810@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Nick Piggin , Rik van Riel , Zach Brown , Anton Altaparmakov , Suparna Bhattacharya , Christoph Hellwig , Hugh Dickins , Jared Hulbert , Chris Mason , "Martin J. Bligh" , Trond Myklebust , Neil Brown , Joern Engel , Miklos Szeredi , Mingming Cao , Linux Memory Management List , linux-fsdevel@vger.kernel.org, Evgeniy Polyakov , Steven Whitehouse , Dave McCracken , Peter Zijlstra To: David Chinner Return-path: Received: from lazybastard.de ([212.112.238.170]:45292 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753764AbXGFK7Q (ORCPT ); Fri, 6 Jul 2007 06:59:16 -0400 Content-Disposition: inline In-Reply-To: <20070706100110.GD12413810@sgi.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 6 July 2007 20:01:10 +1000, David Chinner wrote: > On Fri, Jul 06, 2007 at 04:26:51AM +0200, Nick Piggin wrote: > >=20 > > Keep in mind that the way to get the most out of this meeting > > is for the fs people to have topics of the form "we'd really > > like to do X, can we get some help from the VM"? Or vice versa > > from vm people. >=20 > *nod* >=20 > But, surprisingly enough, the above work is relevent to this forum > because of two things: >=20 > - we've had to move to direct I/O and user space caching to > work around deficiencies in kernel block device caching > under memory pressure.... >=20 > - we've exploited techniques that XFS supports but the VM > does not. i.e. priority tagging of cached metadata so that > less important metadata is tossed first (e.g. toss tree > leaves before nodes and nodes before roots) when under > memory pressure. And the latter is exactly what logfs needs as well. You certainly have me interested. I believe it applies to btrfs and any other cow-fs as well. The point is that higher levels get dirtied by writing lower layers. So perfect behaviour for sync is to write leaves first, then nodes, then the root. Any other order will either cause sync not to sync or cause unnecessary writes and cost performance. J=C3=B6rn --=20 Public Domain - Free as in Beer General Public - Free as in Speech BSD License - Free as in Enterprise Shared Source - Free as in "Work will make you..." - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html