From owner-freebsd-current  Mon Mar  1 10:39:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 8517A15632
	for <current@freebsd.org>; Mon,  1 Mar 1999 10:39:28 -0800 (PST)
	(envelope-from alc@cs.rice.edu)
Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219])
	by cs.rice.edu (8.9.0/8.9.0) with ESMTP id MAA04049;
	Mon, 1 Mar 1999 12:39:06 -0600 (CST)
Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id MAA89683; Mon, 1 Mar 1999 12:39:06 -0600 (CST)
Date: Mon, 1 Mar 1999 12:39:06 -0600
From: Alan Cox <alc@cs.rice.edu>
To: "Richard Seaman, Jr." <dick@tar.com>
Cc: current@freebsd.org
Subject: Re: lockmgr panic with mmap()
Message-ID: <19990301123906.B89033@nonpc.cs.rice.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Until you modify the map, an exclusive lock on the map is overkill.  Try
using read locks.  (See vm_map_lookup.)

In the meantime, I can't see any reason why mincore acquires an
exclusive lock either.  (It never modifies the map.)  I'm going
to remedy that.

	Alan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message