From owner-freebsd-hackers Wed Dec 8 14:21:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9ABCA150F8 for ; Wed, 8 Dec 1999 14:21:39 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA20332; Wed, 8 Dec 1999 14:51:17 -0800 (PST) Date: Wed, 8 Dec 1999 14:51:17 -0800 (PST) From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Getting a new MAP_ flag into mmap() prior to 4.x freeze In-Reply-To: <199912081721.JAA37897@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, Matthew Dillon wrote: > I would like to add a new MAP_ flag to mmap() prior to the 4.x freeze. > The purpose of the flag is to prevent the syncer from syncing the > file underlying the map. The VM system will still page to the file as > needed and, of course, the data will remain consistent with the file. > > This will allow normal files to be used to back (for example) shared > memory without incuring the extra overhead that sync causes every 30 > seconds. Currently it is not possible to use normal files in this > fashion (verses using MAP_ANON, for which sharability is limited, or > SysV shared memory which often has unexpected limitations) and still > have an efficient system. > > The flag will be called MAP_NOSYNC > > Operationally, the syncer will not sync the file while any mmap()'s > exist with that flag set. Once such flagged maps go away, the syncer > will be able to sync the file (if it still exists). > > Comments are welcome. I'd like to see this happen, go for it! :) Don't forget how getnewbuf refils the buffers though, it will need to somehow to communicate to the syncer to disregard MAP_NOSYNC during a shortage... ? :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message