From owner-freebsd-hackers Tue Mar 5 15:56:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA08867 for hackers-outgoing; Tue, 5 Mar 1996 15:56:48 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA08860 for ; Tue, 5 Mar 1996 15:56:43 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id SAA23664; Tue, 5 Mar 1996 18:52:36 GMT From: "John S. Dyson" Message-Id: <199603051852.SAA23664@dyson.iquest.net> Subject: Re: -current MMAP vs INN 1.4unoff3 To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Tue, 5 Mar 1996 18:52:35 +0000 () Cc: hackers@freebsd.org In-Reply-To: from "Jaye Mathisen" at Mar 5, 96 02:34:58 pm 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 Precedence: bulk > > > It's still broken, exhibits the same behaviour as a 2.1-release box, > where it has problems with the active file. > > It would be nice if this would eventually get fixed, even if just for > correctness sake, as opposed to any measurable performance increase. > > There have been significant bugfixes in -current mmap. I wish we had a good model as to what is going on with the mmap code. I am running with an mmaped active file, but only have a partial feed. I used to have problems, but they have gone away for me. How current are you running? John