From: Al Boldi Subject: Re: Allocation strategy - dynamic zone for small files Date: Tue, 14 Nov 2006 21:23:33 +0300 Message-ID: <200611142123.33421.a1426z@gawab.com> References: <1163426218.3343.10.camel@avishay.fsl.cs.sunysb.edu.fsl.cs.sunysb.edu> <200611141959.43417.a1426z@gawab.com> <20061114172659.GC19143@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.70.35.232] ([212.70.35.232]:63360 "EHLO raad.intranet") by vger.kernel.org with ESMTP id S966042AbWKNSVw (ORCPT ); Tue, 14 Nov 2006 13:21:52 -0500 To: Matthew Wilcox In-Reply-To: <20061114172659.GC19143@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 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. I don't think an API is a platitude. google API and you may know what I mean. > Show examples, show how it would help. This thread is an example. > Take the inetd.conf example. Look at the current > user-space parser. Show how a new implementation might work. Plugins are nothing new. And are known to work. > Use pseudocode where necessary; this doesn't have to compile, it has to > convince people that there's something worthwhile in doing this. The important part is to convince those who ACK. IMHO, anyway. Thanks! -- Al