From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?J=F6rn?= Engel Subject: Re: Allocation strategy - dynamic zone for small files Date: Tue, 14 Nov 2006 14:15:21 +0100 Message-ID: <20061114131521.GA30630@wohnheim.fh-wedel.de> References: <20061113193816.GA31700@filer.fsl.cs.sunysb.edu> <20061113235749.GK6012@schatzie.adilger.int> <1163470783.24187.11.camel@kleikamp.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andreas Dilger , Ihar `Philips` Filipau , Bryan Henderson , Josef Sipek , avishay , linux-fsdevel@vger.kernel.org Return-path: Received: from wohnheim.fh-wedel.de ([213.39.233.138]:49794 "EHLO wohnheim.fh-wedel.de") by vger.kernel.org with ESMTP id S933427AbWKNNRJ (ORCPT ); Tue, 14 Nov 2006 08:17:09 -0500 To: Dave Kleikamp Content-Disposition: inline In-Reply-To: <1163470783.24187.11.camel@kleikamp.austin.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 13 November 2006 20:19:43 -0600, Dave Kleikamp wrote: >=20 > I would agree that if the focus is on files that are 128 bytes or > smaller, storing the data in the inode makes the most sense. I don't > think it's worth the complexity to doing any kind of tail merging unl= ess > you would expect that a large number of small files would be too big = to > practically fit in the inode, but small enough that it is worth doing > something to store them efficiently. Symbolic links have been stored > this way for a long time. Logfs did this from the beginning, works like a charm. The only problem I see with this approach is that it is an incompatible change for existing filesystems. So using an old Knoppix CD to rescue a such a filesystem just won't work. J=F6rn --=20 Joern's library part 14: http://www.sandpile.org/ - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html