If you're worried about the overhead of calling pthread_lock and
pthread_unlock under the covers when it's not needed (like on the prefork MPM)
then I would say that's not a big problem. Locking mutexes that are not
contended for can be quite cheap, and often those calls do not even translate
On Friday, December 13, 2002, at 10:05 AM, [EMAIL PROTECTED] wrote:
They are in apr_private.h.
Yes, but they are also in apr.h.
pigmy:~/apr/include - 9:57AM% grep _IS_GLOBAL apr.h
#define APR_PROCESS_LOCK_IS_GLOBAL0
#define APR_PROC_MUTEX_IS_GLOBAL 0
pigmy:~/apr/include - 9:57AM%
*/
/* #undef SYSVSEM_IS_GLOBAL */
/* #undef FCNTL_IS_GLOBAL */
/* #undef FLOCK_IS_GLOBAL */
-Madhu
-Original Message-
From: Greg Ames [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 12, 2002 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [PATCH] Use mutex locks in mod_specweb99.c
Sander Temme
MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
same on HP-UX also.. This is how it looks :
/* Cross process serialization techniques */
/* #undef USE_FLOCK_SERIALIZE */
#define USE_SYSVSEM_SERIALIZE 1
/* #undef USE_FCNTL_SERIALIZE */
/* #undef USE_PROC_PTHREAD_SERIALIZE */
/* #undef
I started seeing the following errors in the specweb99 run output, when I
use mod_specweb99.c with Apache 2.0.43 and worker MPM. The following patch
seems to get rid of the problem. If you're thinking that it may degrade the
response - I did not find much difference though.
Can somebody please
)
Cc: [EMAIL PROTECTED]
Subject: Re: [PATCH] Use mutex locks in mod_specweb99.c
I started seeing the following errors in the specweb99 run
output, when I
use mod_specweb99.c with Apache 2.0.43 and worker MPM. The
following patch
seems to get rid of the problem. If you're thinking that it
may
