Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Jun 2002 05:35:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Jun 2002 05:35:07 -0400 Received: from pc-62-31-66-56-ed.blueyonder.co.uk ([62.31.66.56]:50048 "EHLO sisko.scot.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 20 Jun 2002 05:35:06 -0400 Date: Thu, 20 Jun 2002 10:34:29 +0100 From: "Stephen C. Tweedie" To: Daniel Phillips Cc: Christopher Li , "Stephen C. Tweedie" , Alexander Viro , DervishD , Linux-kernel , ext2-devel@lists.sourceforge.net Subject: Re: [Ext2-devel] Re: Shrinking ext3 directories Message-ID: <20020620103429.A2464@redhat.com> References:

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from phillips@bonn-fries.net on Thu, Jun 20, 2002 at 12:49:57AM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 993 Lines: 25 Hi, On Thu, Jun 20, 2002 at 12:49:57AM +0200, Daniel Phillips wrote: > I don't have code, but let me remind you of this post: > > http://marc.theaimsgroup.com/?l=ext2-devel&m=102132142032096&w=2 > > A sketch of the coalescing design is at the end. I'll formalize that. One question --- just how stable will this be if we boot into a kernel that doesn't have the coalescing enabled, and start modifying directories? We _could_ just teach the current code to clear those top 8 bits in the parent any time we touch a leaf node, but that's unnecessarily expensive, so we'd really need to have some way of either recreating the hint fields from scratch every so often, or of spotting when they have become badly out-of-date. Cheers, Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/