From: Nick Piggin Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available Date: Sun, 15 Mar 2009 15:14:27 +1100 Message-ID: <200903151514.28145.nickpiggin@yahoo.com.au> References: <200903110925.37614.phillips@phunq.net> <200903151450.51726.nickpiggin@yahoo.com.au> <200903142108.53155.phillips@phunq.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Matthew Wilcox , linux-fsdevel@vger.kernel.org, tux3@tux3.org, Andrew Morton , linux-kernel@vger.kernel.org To: Daniel Phillips Return-path: Received: from smtp103.mail.mud.yahoo.com ([209.191.85.213]:33188 "HELO smtp103.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751216AbZCOEOi (ORCPT ); Sun, 15 Mar 2009 00:14:38 -0400 In-Reply-To: <200903142108.53155.phillips@phunq.net> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sunday 15 March 2009 15:08:52 Daniel Phillips wrote: > On Saturday 14 March 2009, Nick Piggin wrote: > > On Sunday 15 March 2009 14:24:29 Daniel Phillips wrote: > > > I expect implementing VM extents to be a brutally complex project, as > > > filesystem extents always turn out to be, even though one tends to > > > enter such projects thinking, how hard could this be? Answer: harder > > > than you think. But VM extents would be good for a modest speedup, so > > > somebody is sure to get brave enough to try it sometime. > > > > I don't think there is enough evidence to be able to make such an > > assertion. > > > > When you actually implement extent splitting and merging in a deadlock > > free manner and synchronize everything properly I wouldn't be surprised > > if it is slower most of the time. If it was significantly faster, then > > memory fragmentation means that it is going to get significantly slower > > over the uptime of the kernel, so you would have to virtually map the > > kernel and implement memory defragmentation, at which point you get even > > slower and more complex. > > You can make exactly the same argument about filesystem extents, and > we know that extents are faster there. So what is the fundamental > difference? Uh, aside from all the obvious fundamental differences there are, you can only make such an assertion if performance characteristics and usage patterns are very similar, nevermind fundamentally different...