dgaudet 97/09/30 16:24:50
Modified: src PORTING
Log:
document new serialization stuff
Revision Changes Path
1.13 +24 -3 apachen/src/PORTING
Index: PORTING
===================================================================
RCS file: /export/home/cvs/apachen/src/PORTING,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- PORTING 1997/09/12 20:13:05 1.12
+++ PORTING 1997/09/30 23:24:49 1.13
@@ -205,17 +205,38 @@
USE_FCNTL_SERIALIZED_ACCEPT:
Define if the OS requires a mutex "lock" around the socket accept()
- call. Use fcntl() locking.
+ call. Use fcntl() locking. See htdocs/manual/misc/perf-tuning.html.
USE_FLOCK_SERIALIZED_ACCEPT:
Define if the OS requires a mutex "lock" around the socket accept()
call. Use flock() locking (fcntl() is expensive on some OSs, esp.
- when using NFS).
+ when using NFS). See htdocs/manual/misc/perf-tuning.html.
+
+ USE_USLOCK_SERIALIZED_ACCEPT:
+ Probably IRIX only: use uslock() to serialize, which is far faster
+ on multiprocessor boxes (and far slower on uniprocessor, yay).
+ See htdocs/manual/misc/perf-tuning.html.
+
+ USE_SYSVSEM_SERIALIZED_ACCEPT:
+ Use System V semaphores to serialize accept. These are problematic
+ in that they won't be cleaned up if apache is kill -9d, and there's
+ the potential of a CGI causing a denial of service attack if it's
+ running as the same uid as apache (i.e. suexec is recommended on
+ public servers).
+ See htdocs/manual/misc/perf-tuning.html.
+
+ USE_PTHREADS_SERIALIZED_ACCEPT:
+ Use POSIX mutexes to serialize accept.
+ See htdocs/manual/misc/perf-tuning.html.
+
+ SAFE_UNSERIALIZED_ACCEPT:
+ It's safe to unserialize single-socket accept().
+ See htdocs/manual/misc/perf-tuning.html.
USE_LONGJMP:
Define to use the longjmp() call instead of siglongjmp()
(as well as setjmp() instead of sigsetjmp()).
-
+
USE_MMAP_FILES:
Enable the use of mmap() for sending static files.
