[patch] apache-2.0.58.patch

apache-2.0.58.patch (text/plain), 1.72 KB, created by MT on 2007-01-30 15:49:48 UTC

--- apache-2.0.58-r2.ebuild	2007-01-24 13:49:08.621948127 +0100
+++ apache-2.0.58-r2.ebuild	2007-01-27 15:32:40.789159981 +0100
@@ -112,6 +112,10 @@
 	local modtype
 	if useq static-modules; then
 		modtype="static"
+
+		# This will save RAM that's allocated only for supporting dynamically
+		# loaded modules (we are using static modules, so we do not need to allocate extra RAM).
+		CFLAGS="${CFLAGS} -DDYNAMIC_MODULE_LIMIT=0"
 	else
 		modtype="shared"
 	fi
@@ -163,6 +167,29 @@
 			--with-program-name=apache2 \
 			--with-devrandom=/dev/urandom \
 			--host=${CHOST} ${MY_BUILTINS}"
+	
+	# Atomic Operations
+	# Some modules, such as mod_cache, use APR's atomic API. This API provides
+	# atomic operations that can be used for lightweight thread synchronization.
+	# By default, APR implements these operations using the most efficient
+	# mechanism available on each target OS/CPU platform. Many modern CPUs, for
+	# example i486 and greater archs, have an instruction that does an atomic 
+	# compare-and-swap (CAS) operation in hardware. However Apache defaults to a slower,
+	# mutex-based implementation of the atomic API in order to ensure
+	# compatibility with older CPU models that lack such instructions.
+	# Here we try to detect if you are building Apache from one of these platforms,
+	# and select a faster atomic implementation by overriding Apache defaults with the:
+	# --enable-nonportable-atomics option.
+	# NOTE: nonportable-atomics increasing Apache performances and scalability.
+	case ${CHOST} in
+    	i386*) 
+			;;
+        *)  ebegin "Setting faster APR Atomic Operations"
+				myconf="${myconf} \
+				            --enable-nonportable-atomics=yes"
+			eend $?
+			;;
+    esac
 
 	# debugging support
 	if useq debug ; then