From owner-freebsd-hackers Thu Dec 7 13:40:26 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA24109 for hackers-outgoing; Thu, 7 Dec 1995 13:40:26 -0800 (PST) Received: from snoopy.mv.com (snoopy.mv.com [199.125.64.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA24006 Thu, 7 Dec 1995 13:40:07 -0800 (PST) Received: (from pw@localhost) by snoopy.mv.com (8.6.11/8.6.9) id PAA01020; Thu, 7 Dec 1995 15:31:42 -0500 Date: Thu, 7 Dec 1995 15:31:42 -0500 From: "Paul F. Werkowski" Message-Id: <199512072031.PAA01020@snoopy.mv.com> To: John Dyson Cc: root@buffnet.net (Steve Hovey), terry@lambert.org, jau@jau.csc.fi, questions@freebsd.org, hackers@freebsd.org Subject: Re: Any operational code using mmap() on FreeBSD ? In-Reply-To: <199512071439.GAA16815@freefall.freebsd.org> References: <199512071439.GAA16815@freefall.freebsd.org> Sender: owner-hackers@freebsd.org Precedence: bulk >>>>> "John" == John Dyson writes: >> MMAP under freebsd 2.05-R is broken. I run an INN news server >> on 2.0.5R and if I compiled it using MMAP, the correct values >> were not maintained in the active file. This problems occurred >> when usage got to the size that virtual ram swapping came into >> play. >> John> Yep, there are some problems -- the code in current is John> better. The problem has to do with entirely bogus msync John> code. (That I wrote.) Also, don't *even* think about using John> NFS and mmap for writable regions in 2.0.5. I have been running a Lisp system that relies on mmap for its dynamic space on 2.0.5 since the CDROM was released. Sometimes the VM gets to over 100 MB and with 16MB RAM the vm system really gets stressed. Never had a problem or a crash though. In fact I am overdue in congratulating the vm hackers for such a great system. Congrats!!! Now 1.1.5 was a different story altogether. Paul ------------ Paul Werkowski ANSI Common Lisp on Intel/FreeBSD? pw@snoopy.mv.com http://www.mv.com/users/pw/lisp