Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Errors-To: <wrowe@rowe-clan.net>
Message-ID: <17e901c11b5c$de4b9100$93c0b0d0@roweclan.net>
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: <new-httpd@apache.org>
References: <3B33B2B2.40800@pacbell.net>
 <114401c11ab2$348fe170$93c0b0d0@roweclan.net> <3B691549.7040306@pacbell.net>
Subject: Re: [PATCH] Re: directory_walk performance
Date: Thu, 2 Aug 2001 09:08:23 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Status: O

From: "Brian Pane" <bpane@pacbell.net>
Sent: Thursday, August 02, 2001 3:54 AM


> Here's a patch that implements my pre-merge optimization to
> reduce (and in some cases completely eliminate) the calls to
> ap_merge_per_dir_configs.  Its impacts on directory_walk are
> minor; all the real work happens in a new post-config-phase
> function.


Another glitch.  If the source is from the cache, we can't trust that elements
of base or add allocated will still in memory when the cache is called :(  Not
unless we also discard all decendants when we refresh the cache.  This implies
that we need a protected refcount for each of the cached elements, not only by
the request that is relying on the data, but the straight down the chain.

Bill