From owner-freebsd-current  Wed Dec 11 10:01:21 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id KAA25583
          for current-outgoing; Wed, 11 Dec 1996 10:01:21 -0800 (PST)
Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA25578
          for <current@freebsd.org>; Wed, 11 Dec 1996 10:01:19 -0800 (PST)
Received: by freebsd.netcom.com (8.6.12/SMI-4.1)
	id MAA00824; Wed, 11 Dec 1996 12:00:47 -0600
From: bugs@freebsd.netcom.com (Mark Hittinger)
Message-Id: <199612111800.MAA00824@freebsd.netcom.com>
Subject: Re: mlocking an mmap'ped region? (fwd)
To: current@freebsd.org
Date: Wed, 11 Dec 1996 12:00:47 -0600 (CST)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > The following does not seem to work on a 2.2-CURRENT box (built yesterday).
> > It does seem to work on SunOS.
> > 
> > Is it just too early to be doing programming or is there really something
> > preventing me from doing this?
> > 
> Yep, it is called broken code :-(.  That problem was just brought to my
> attention yesterday.  Unfortunately, someone also wants it fixed in 2.1.X :-(.
> 
> I'll probably get it fixed in -current in the next day or so.  Doing mlock
> the way that it is currently done is problematical from a couple of viewpoints,
> so I think it is going to need to be reworked.  Basically, the original
> way of doing vm_map_pageable is wrong for userland pages.

Isn't this also a big problem on SMP?  :-)

Later

Mark Hittinger
Netcom/Dallas
bugs@freebsd.netcom.com