From: Al Boldi Subject: Re: Allocation strategy - dynamic zone for small files Date: Tue, 14 Nov 2006 19:59:43 +0300 Message-ID: <200611141959.43417.a1426z@gawab.com> References: <1163426218.3343.10.camel@avishay.fsl.cs.sunysb.edu.fsl.cs.sunysb.edu> <200611141843.39745.a1426z@gawab.com> <20061114154630.GB19143@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: 7bit Cc: Theodore Tso , linux-fsdevel@vger.kernel.org Return-path: Received: from [212.33.180.140] ([212.33.180.140]:57728 "EHLO raad.intranet") by vger.kernel.org with ESMTP id S966207AbWKNQ6L (ORCPT ); Tue, 14 Nov 2006 11:58:11 -0500 To: Matthew Wilcox In-Reply-To: <20061114154630.GB19143@parisc-linux.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Matthew Wilcox wrote: > On Tue, Nov 14, 2006 at 06:43:39PM +0300, Al Boldi wrote: > > An API would probably be in order. > > > > Performance due to non-redundancy. > > > > Or a desire to let people choose what they want. > > > > Think freedom... > > How about fewer "visionary statements" and more code? How about discussing the feasibility before sending any code? Thanks! -- Al