From 2b71c841f521c575d2a2dcf03927c2d1c1a3facb Mon Sep 17 00:00:00 2001 From: Alan Cox Date: Thu, 25 Nov 1999 20:21:52 +0000 Subject: [PATCH] Remove nonsensical vm_map_{clear,set}_recursive() calls from vm_map_pageable(). At the point they called, vm_map_pageable() holds a read (or shared) lock on the map. The purpose of vm_map_{clear,set}_recursive() is to disable/enable repeated write (or exclusive) lock requests by the same process. --- sys/vm/vm_map.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c index ca42708f783b..eaa65f7783e9 100644 --- a/sys/vm/vm_map.c +++ b/sys/vm/vm_map.c @@ -1496,7 +1496,6 @@ vm_map_pageable(map, start, end, new_pageable) if (vm_map_pmap(map) == kernel_pmap) { vm_map_unlock(map); /* trust me ... */ } else { - vm_map_set_recursive(map); vm_map_lock_downgrade(map); } @@ -1526,8 +1525,6 @@ vm_map_pageable(map, start, end, new_pageable) if (vm_map_pmap(map) == kernel_pmap) { vm_map_lock(map); - } else { - vm_map_clear_recursive(map); } if (rv) { vm_map_unlock(map);