From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Wilcox <matthew@wil.cx>
Subject: Re: Allocation strategy - dynamic zone for small files
Date: Tue, 14 Nov 2006 08:46:30 -0700
Message-ID: <20061114154630.GB19143@parisc-linux.org>
References: <1163426218.3343.10.camel@avishay.fsl.cs.sunysb.edu.fsl.cs.sunysb.edu> <200611141421.09823.a1426z@gawab.com> <20061114142553.GB30961@thunk.org> <200611141843.39745.a1426z@gawab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Theodore Tso <tytso@mit.edu>, linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from palinux.external.hp.com ([192.25.206.14]:19164 "EHLO
	mail.parisc-linux.org") by vger.kernel.org with ESMTP
	id S966108AbWKNPqb (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 14 Nov 2006 10:46:31 -0500
To: Al Boldi <a1426z@gawab.com>
Content-Disposition: inline
In-Reply-To: <200611141843.39745.a1426z@gawab.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

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?  Or at least an
architecture description.  Or a rough prototype that shows how we can
make some improvements.  You're looking remarkably content-free right now.