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 17:57:49 +0200 Message-ID: <20070706155748.GC846@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> <20070706102623.GA846@lazybastard.org> <20070706134201.GL31489@sgi.com> <20070706095214.1ac9da94@think.oraclecorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Chinner , =?utf-8?B?SsODwrZybg==?= Engel , Nick Piggin , Rik van Riel , Zach Brown , Anton Altaparmakov , Suparna Bhattacharya , Christoph Hellwig , Hugh Dickins , Jared Hulbert , "Martin J. Bligh" , Trond Myklebust , Neil Brown , Miklos Szeredi , Mingming Cao , Linux Memory Management List , linux-fsdevel@vger.kernel.org, Evgeniy Polyakov , Steven Whitehouse , Dave McCracken , Peter Zijlstra To: Chris Mason Return-path: Received: from lazybastard.de ([212.112.238.170]:52233 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760918AbXGFQBw (ORCPT ); Fri, 6 Jul 2007 12:01:52 -0400 Content-Disposition: inline In-Reply-To: <20070706095214.1ac9da94@think.oraclecorp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 6 July 2007 09:52:14 -0400, Chris Mason wrote: > On Fri, 6 Jul 2007 23:42:01 +1000 David Chinner wrote: >=20 > > Hmmm - I guess you could use it for writeback ordering. I hadn't > > really thought about that. Doesn't seem a particularly efficient wa= y > > of doing it, though. Why not just use multiple address spaces for > > this? i.e. one per level and flush in ascending order. Interesting idea. Is it possible to attach several address spaces to a= n inode? That would cure some headaches. > At least in the case of btrfs, the perfect order for sync is disk > order ;) COW happens when blocks are changed for the first time in a > transaction, not when they are written out to disk. If logfs is > writing things out some form of tree order, you're going to have to > group disk allocations such that tree order reflects disk order someh= ow. I don't understand half of what you're writing. Maybe we should do another design session on irc? At any rate, logfs simply writes out blocks. When it is handed a page to write, the corresponding block is written. Allocation happens at writeout time, not earlier. Each written block causes a higher-level block to get changed, so that is written immediatly as well, until the next higher level is the inode. I would like to instead just dirty the higher-level block, so that multiple changes can accumulate before indirect blocks are written. An= d I have no idea how transactions relate to all this. > But, the part where we toss leaves first is definitely useful. Shouldn't LRU ordering already do that. I can even imagine cases when leaves should be tossed last and LRU ordering would dtrt. J=C3=B6rn --=20 The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility, and among other things he avoids clever tricks like the plagu= e. -- Edsger W. Dijkstra - 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