From owner-freebsd-hackers Wed Dec 16 11:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28434 for freebsd-hackers-outgoing; Wed, 16 Dec 1998 11:27:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28428 for ; Wed, 16 Dec 1998 11:27:40 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id OAA16907 for ; Wed, 16 Dec 1998 14:27:22 -0500 (EST) Date: Wed, 16 Dec 1998 14:27:21 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Question on lock Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. -------------------------------------------------- | 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