From owner-freebsd-hackers Fri Jul 19 14:17:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20032 for hackers-outgoing; Fri, 19 Jul 1996 14:17:56 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20024 for ; Fri, 19 Jul 1996 14:17:52 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id QAA00678; Fri, 19 Jul 1996 16:16:38 -0500 (EST) From: John Dyson Message-Id: <199607192116.QAA00678@dyson.iquest.net> Subject: Re: RE:About buffer cache To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 19 Jul 1996 16:16:38 -0500 (EST) Cc: lada@ws2301.gud.siemens.co.at, heo@cslsun10.sogang.ac.kr, hackers@FreeBSD.org In-Reply-To: <199607191826.NAA09117@brasil.moneng.mei.com> from "Joe Greco" at Jul 19, 96 01:26:06 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 X-Loop: FreeBSD.org Precedence: bulk > > > Even though, an implementation of madvise(2) which turns on the sequential > > access policy for the mmap(2)ped file wouldn't be bad either. > > I mentioned support for madvise() a while back to John Dyson and he > suggested that it would be a weekend project, I have not checked back on > this but I may have reason to do so pretty soon. > > madvise() is perfect for these sorts of applications. > Madvise is now mostly implemented in current (for the last couple of months.) John