From owner-freebsd-hackers  Mon Jul 19 13:48:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4D9CD152EB
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 19 Jul 1999 13:48:18 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA99660;
	Mon, 19 Jul 1999 13:48:16 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 19 Jul 1999 13:48:16 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907192048.NAA99660@apollo.backplane.com>
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Anything special with kmem_map and mb_map?
References:  <379385BE.31A9F78@cs.binghamton.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:I have been wondering this for some time.   There are many kernel
:submaps: exec_map, clean_map,
:etc.  But if you look the code in vm_map_find(), we have to call splvm()
:for kmem_map and its
:submap mb_map, but not for other kernel submaps.  So is there anything
:special with these two
:kernel submaps?
:
:Thanks for any help.
:
:-Zhihui

    The kmem_map and mb_map's can be modified from interrupts.  
    The other maps cannot.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


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