From owner-freebsd-hackers  Mon Jan  8 15:09:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA16367
          for hackers-outgoing; Mon, 8 Jan 1996 15:09:19 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16350
          for <hackers@freebsd.org>; Mon, 8 Jan 1996 15:09:14 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id PAA01556; Mon, 8 Jan 1996 15:09:13 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id PAA04708; Mon, 8 Jan 1996 15:09:15 -0800 (PST)
Message-Id: <199601082309.PAA04708@corbin.Root.COM>
To: Terry Lambert <terry@lambert.org>
cc: gpalmer@westhill.cdrom.com, wosch@cs.tu-berlin.de, hackers@freebsd.org
Subject: Re: large files 
In-reply-to: Your message of "Mon, 08 Jan 96 15:41:36 MST."
             <199601082241.PAA10640@phaeton.artisoft.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 08 Jan 1996 15:09:15 -0800
Sender: owner-hackers@freebsd.org
Precedence: bulk

>Actually, John says it does.  As I stated in my followup to John, I
>screwed up SHMEM and SHLIB thikning about mmap() as the underlying
>implementation mechanism.

   Time for me to correct something I said in my last response. Our current
implementation of SYSVSHM does actually store it's data in a named anonymous
memory region/object and it does this by using the internal version of "mmap".
...but his has nothing to do with supporting large files and doesn't in itself
having anything to do with why SYSVSHM memory objects consume kernel VM.
Anyway, I suppose I shouldn't have bothered responding to any of this. Sigh.

-DG

David Greenman
Core Team/Principal Architect, The FreeBSD Project