From d40d033ac01faffc602ac83b9837ada8d4d625e4 Mon Sep 17 00:00:00 2001 From: Robert Watson Date: Mon, 22 Mar 2004 16:37:32 +0000 Subject: [PATCH] Commit a message to UPDATING indicating that during network stack locking merges, debug.mpsafenet will no longer be safe to use, and that it should be turned off (which is the default). I will commit a follow-up message to UPDATING (and post to freebsd-current) when it's safe to turn it on, with a description of under what circumstances it is safe to use. --- UPDATING | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/UPDATING b/UPDATING index c2d371486f4..8ee04d8d816 100644 --- a/UPDATING +++ b/UPDATING @@ -17,6 +17,17 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW: developers choose to disable these features on build machines to maximize performance. +20040322: + The debug.mpsafenet tunable controls whether the kernel Giant + lock is held across the lower levels of the network stack, and + by default is turned off. In the few days following 20040322, + the behavior of debug.mpsafenet will change such that this + tunable controls Giant over all levels of the network stack. + If you are currently setting debug.mpsafenet to 1, you should + set it back to 0 (the default) again during the change-over. + An additional note will be added to UPDATING when sufficient + locking is merged to permit this to take place. + 20040310: The FreeBSD/sparc64 platform is changing time_t from 32-bits to 64-bits. This is a very major incompatible change, so people