Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Content-Type: text/plain;
  charset="iso-8859-1"
From: Ryan Bloom <rbb@covalent.net>
Reply-To: rbb@covalent.net
Organization: Covalent Technologies
To: new-httpd@apache.org, Brian Pane <bpane@pacbell.net>
Subject: Re: [Patch]: Scoreboard as linked list.
Date: Sat, 4 Aug 2001 13:26:39 -0700
References: <3B6A0BD4.E54E56BF@raleigh.ibm.com>
 <3B6AA085.2ED9B0CF@raleigh.ibm.com> <3B6C53B5.10505@pacbell.net>
In-Reply-To: <3B6C53B5.10505@pacbell.net>
MIME-Version: 1.0
Message-Id: <01080413263902.01076@koj.rkbloom.net>
Content-Transfer-Encoding: 8bit
Status: O

On Saturday 04 August 2001 12:57, Brian Pane wrote:
> Paul J. Reder wrote:
> >Brian Pane wrote:
>
> [...]
>
> >>Also, the documentation
> >>that Paul posted mentions the option of using per-process or
> >>per-worker locking; that might offer sufficiently small granularity,
> >>depending on what specifically your modules are doing with the
> >>scoreboard.
> >>--Brian
> >
> >Again, this is a possibility, *if* performance requires it. Using
> >finer granularity locking adds complexity to the code. I would
> >discourage moving to this unless the current scheme proves to be
> >a problem.
>
> I'm fundamentally in agreement.  My point was not that finer-grained
> locking is inherently necessary, but rather that the ability of your
> design to support finer-grained locking refutes Ryan's theoretical
> concern about locking being a fundamental bottleneck.

Understand, this isn't a theoretical concern for me.   I have modules that walk the scoreboard
on every request.  They are looking to determine what each of the other workers is doing.
Requiring any locking to walk the scoreboard is a non-starter.

Are there other ways to handle what I need to do?  Yes.  They add greatly to the complexity of
my code.  I have also posted two other problems with the current patch.  One is a simple bug that
Paul is fixing, the other is a fundamental design flaw that also requires I give the patch a -1.

Ryan

_____________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
Covalent Technologies			rbb@covalent.net
-----------------------------------------------------------------------------