apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerenkra...@apache.org
Subject cvs commit: apr STATUS
Date Tue, 17 Jul 2001 05:43:54 GMT
jerenkrantz    01/07/16 22:43:53

  Modified:    .        STATUS
  Log:
  Add note about the gmtime_r mutex on Solaris.
  I'm sure there are other bad libc calls out there, but this is the one
  I see right now.
  
  Revision  Changes    Path
  1.50      +10 -1     apr/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apr/STATUS,v
  retrieving revision 1.49
  retrieving revision 1.50
  diff -u -r1.49 -r1.50
  --- STATUS	2001/07/16 08:06:14	1.49
  +++ STATUS	2001/07/17 05:43:53	1.50
  @@ -1,5 +1,5 @@
   APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS:			-*-text-*-
  -Last modified at [$Date: 2001/07/16 08:06:14 $]
  +Last modified at [$Date: 2001/07/17 05:43:53 $]
   
   Release:
   
  @@ -177,6 +177,15 @@
                   There are other possibilities.  Any of those probably 
                   work as well.  See the apr archives for more info.  
                   We're still debating this.
  +
  +    * Possible gmtime_r replacement in explode_time
  +      On Solaris (and possibly others), the gmtime_r libc function obtains
  +      a mutex.  We have seen 21/25 threads being blocked in this mutex on 
  +      a threaded httpd MPM when requesting static pages.  It may be worth 
  +      it to hand optimize this since there is no real need for a mutex at 
  +      the system level (straight arithmetic from what I can tell).  If you 
  +      have access to the Solaris source code:
  +        osnet_volume/usr/src/lib/libc/port/gen/time_comm.c.
   
   Documentation that needs writing:
   
  
  
  

Mime
View raw message