From owner-freebsd-hackers  Tue Dec 10 19:33:07 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id TAA04485
          for hackers-outgoing; Tue, 10 Dec 1996 19:33:07 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA04479
          for <hackers@freebsd.org>; Tue, 10 Dec 1996 19:33:03 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id WAA01277; Tue, 10 Dec 1996 22:31:27 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199612110331.WAA01277@dyson.iquest.net>
Subject: Re: Multiple Buffer allocation of Shared Memory
To: terry@lambert.org (Terry Lambert)
Date: Tue, 10 Dec 1996 22:31:27 -0500 (EST)
Cc: scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org
In-Reply-To: <199612102114.OAA04855@phaeton.artisoft.com> from "Terry Lambert" at Dec 10, 96 02:14:43 pm
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Practically, the shm stuff is mapped in KVM space and the mmap stuff
> is not.
>
I fixed that brokenness in 2.2 and 3.0 a long time ago.

>
>  This is an implemenation detail (it's worse to implement
> address space mappings in the KVM space because it's already so
> limited and has paging restrictions because of the processor protect
> bits -- but it's possible and likely for this to fixed in a future
> rev of FreeBSD).
> 
It is fixed :-).  We are very very KVA space conservative (or getting
more so with larger and larger systems looming.)

John