Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 14943 invoked by uid 500); 21 May 2001 20:51:56 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 14900 invoked from network); 21 May 2001 20:51:54 -0000 Date: Mon, 21 May 2001 13:51:56 -0700 (PDT) From: dean gaudet To: Subject: Re: Scoreboard redesign In-Reply-To: Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Sun, 20 May 2001 rbb@covalent.net wrote: > Having said that, the locking issue is a much bigger deal with linked > lists than was mentioned on-list last week. The child process will > have to walk the list whenever mod_status is called, which means that > the child process will have to lock the scoreboard while serving > status requests. there are concurrency issues no matter what you do. consider what happens if one processor is half-way through setting up the request uri when another process tries to make a /server-status page out of it. (even the "safe access" foo for the vhostrec in 1.3's scoreboard is not really safe... it would need volatiles and memory barriers to be safe.) -dean