Subject: Re: [PATCH 1/3] ext3 reservation remove stale window fix
From: Mingming Cao <cmm@us.ibm.com>
To: Matt Mackall <mpm@selenic.com>
Cc: akpm@osdl.org, "Stephen C. Tweedie" <sct@redhat.com>,
       Badari Pulavarty <pbadari@us.ibm.com>,
       linux-kernel <linux-kernel@vger.kernel.org>,
       "ext2-devel@lists.sourceforge.net" <ext2-devel@lists.sourceforge.net>
In-Reply-To: <20041018234126.GB28904@waste.org>
References: <1098140107.8803.1062.camel@w-ming2.beaverton.ibm.com> 
	<20041018234126.GB28904@waste.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 18 Oct 2004 18:11:16 -0700
Message-Id: <1098148283.9754.1090.camel@w-ming2.beaverton.ibm.com>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1041
Lines: 22

On Mon, 2004-10-18 at 16:41, Matt Mackall wrote:
> On Mon, Oct 18, 2004 at 03:55:04PM -0700, Mingming Cao wrote:
> > 
> > Before we changed the per-filesystem reservations from a linked list
> > to a red-black tree, in order to speed up the linear search from the
> > list head, we keep the current(stale) reservation window as a
> > reference pointer to skip the nodes prior to the current/stale
> > window node, when failed to allocate a new window in current group
> > and try to do allocation in next group.
> 
> One wonders whether a prio tree of the sort used by the current VMA
> searching code would be a better match to the problem than the
> red-black approach.

Could you please elaborate more? I think the current VMA code is using
red-black tree in their searching code(find_vma()).

-
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/