Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Wed, 22 May 2002 11:26:48 -0700
From: Aaron Bannert <aaron@clove.org>
To: dev@httpd.apache.org
Cc: dev@apr.apache.org
Subject: Re: [PATCH 2] worker MPM deadlock
Message-ID: <20020522112648.F26886@clove.org>
Mail-Followup-To: Aaron Bannert <aaron@clove.org>, dev@httpd.apache.org,
	dev@apr.apache.org
References: <20020522110806.E26886@clove.org>
 <Pine.LNX.4.44.0205221410430.21845-100000@deepthought.cs.virginia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <Pine.LNX.4.44.0205221410430.21845-100000@deepthought.cs.virginia.edu>
User-Agent: Mutt/1.3.23i

On Wed, May 22, 2002 at 02:14:30PM -0400, Cliff Woolley wrote:
> If it isn't guaranteed to do something but is rather just a "hint", that's
> fine, as long as it's documented.  But we should still make an attempt to
> honor the hint if the underlying system will let us.
> 
> [For example, I know my research work frequently requires these hints
> because ~10ms is farrrrr too long a timeslice in my field, and I love
> using APR for my research projects... I personally just assumed
> apr_thread_yield() did what I wanted until I looked into it and found that
> it did nothing.]

[moving this discussion to APR]

FWIW, here's the top of the thread that introduced this API:

http://www.apachelabs.org/apr-mbox/200107.mbox/%3csb655900.070@prv-mail20.provo.novell.com%3e

You bring up a good point, so my only question is whether we know how
to implement this on all the unix thread libraries out there.

-aaron