Rename SI_SUB_MUTEX to SI_SUB_MTX_POOL to make the name at all accurate.

While doing this, move it earlier in the sysinit boot process so that the
VM system can use it.

After that, the system is now able to use sx locks instead of lockmgr
locks in the VM system.  To accomplish this, some of the more
questionable uses of the locks (such as testing whether they are
owned or not, as well as allowing shared+exclusive recursion) are
removed, and simpler logic throughout is used so locks should also be
easier to understand.

This has been tested on my laptop for months, and has not shown any
problems on SMP systems, either, so appears quite safe.  One more
user of lockmgr down, many more to go :)

1 files changed, 1 insertions, 1 deletions

diff --git a/sys/kern/kern_mtxpool.c b/sys/kern/kern_mtxpool.c
index ee1b64b..f0f1208 100644
--- a/sys/kern/kern_mtxpool.c
+++ b/sys/kern/kern_mtxpool.c
@@ -111,5 +111,5 @@ mtx_pool_unlock(void *ptr)
     mtx_unlock(_mtx_pool_find(ptr));
 }
 
-SYSINIT(mtxpooli, SI_SUB_MUTEX, SI_ORDER_FIRST, mtx_pool_setup, NULL)   
+SYSINIT(mtxpooli, SI_SUB_MTX_POOL, SI_ORDER_FIRST, mtx_pool_setup, NULL)