From owner-freebsd-hackers Wed Dec 16 11:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01946 for freebsd-hackers-outgoing; Wed, 16 Dec 1998 11:51:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01939 for ; Wed, 16 Dec 1998 11:51:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA81012; Wed, 16 Dec 1998 11:50:58 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Dec 1998 11:50:58 -0800 (PST) From: Matthew Dillon Message-Id: <199812161950.LAA81012@apollo.backplane.com> To: zhihuizhang Cc: hackers Subject: Re: Question on lock References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In the comment of vm_map_pageable() in file vm_map.c, there is a following :sentence: : :"Because of problems in the recursive lock package, we cannot upgrade to a :write lock in vm_map_lookup." : :Does the recursive lock package refer to kern_lock.c? There IS a :lock_read_to_write() call in vm_map_lookup(). So why there is such a :problem? Please give me some enlightenment. : :Any help is appreciated. There are probably deadlock problems associated with trying to upgrade the lock at that point. The whole locking methodology used in the kernel really needs a complete rewrite. -Matt :-------------------------------------------------- :| Zhihui Zhang, http://cs.binghamton.edu/~zzhang | :| Dept. of Computer Science, SUNY at Binghamton | :-------------------------------------------------- : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message