From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Allocation strategy - dynamic zone for small files Date: Tue, 14 Nov 2006 10:27:00 -0700 Message-ID: <20061114172659.GC19143@parisc-linux.org> References: <1163426218.3343.10.camel@avishay.fsl.cs.sunysb.edu.fsl.cs.sunysb.edu> <200611141843.39745.a1426z@gawab.com> <20061114154630.GB19143@parisc-linux.org> <200611141959.43417.a1426z@gawab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Theodore Tso , linux-fsdevel@vger.kernel.org Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:3265 "EHLO mail.parisc-linux.org") by vger.kernel.org with ESMTP id S965844AbWKNR1B (ORCPT ); Tue, 14 Nov 2006 12:27:01 -0500 To: Al Boldi Content-Disposition: inline In-Reply-To: <200611141959.43417.a1426z@gawab.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Nov 14, 2006 at 07:59:43PM +0300, Al Boldi wrote: > 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? Great idea. Discuss the feasibility, rather than responding with platitudes to people telling you it's infeasible. Show examples, show how it would help. Take the inetd.conf example. Look at the current user-space parser. Show how a new implementation might work. Use pseudocode where necessary; this doesn't have to compile, it has to convince people that there's something worthwhile in doing this.