From owner-freebsd-current  Tue Mar  2  3:42:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id BBB9A14CCB
	for <current@FreeBSD.ORG>; Tue,  2 Mar 1999 03:42:22 -0800 (PST)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA03136;
	Tue, 2 Mar 1999 22:41:46 +1100
Date: Tue, 2 Mar 1999 22:41:46 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199903021141.WAA03136@godzilla.zeta.org.au>
To: alc@cs.rice.edu, dick@tar.com
Subject: Re: lockmgr panic with mmap()
Cc: current@FreeBSD.ORG
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.

Doesn't it modify the map indirectly vi subyte()?  I think it wants
to prevent modifications, but this is impossible.

Bruce


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