From owner-freebsd-bugs  Mon Sep 30 12:40: 6 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8FE9537B401
	for <freebsd-bugs@hub.freebsd.org>; Mon, 30 Sep 2002 12:40:05 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A5ED643E7B
	for <freebsd-bugs@hub.freebsd.org>; Mon, 30 Sep 2002 12:40:04 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id g8UJe4Co078948
	for <freebsd-bugs@freefall.freebsd.org>; Mon, 30 Sep 2002 12:40:04 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id g8UJe4Xi078947;
	Mon, 30 Sep 2002 12:40:04 -0700 (PDT)
Date: Mon, 30 Sep 2002 12:40:04 -0700 (PDT)
Message-Id: <200209301940.g8UJe4Xi078947@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Garrett Wollman <wollman@lcs.mit.edu>
Subject: Re: bin/43426: mlockall and munlockall system calls are missing from
 FreeBSD
Reply-To: Garrett Wollman <wollman@lcs.mit.edu>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR bin/43426; it has been noted by GNATS.

From: Garrett Wollman <wollman@lcs.mit.edu>
To: Janos Mohacsi <mohacsi@niif.hu>
Cc: <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: bin/43426: mlockall and munlockall system calls are missing from
 FreeBSD
Date: Mon, 30 Sep 2002 15:31:31 -0400 (EDT)

 <<On Mon, 30 Sep 2002 19:45:24 +0200 (CEST), Janos Mohacsi <mohacsi@niif.hu> said:
 
 > Yes I knew that, but I expected that mlockall() can be implemented
 > with usage of mlock(), that does exist on FreeBSD.
 
 Actually, it can't, for the simple reason of mlockall's MCL_FUTURE
 option, which automatically locks all future allocations in addition
 to the ones presently in use.
 
 -GAWollman
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message