From owner-freebsd-hackers@FreeBSD.ORG  Thu Mar 29 20:10:23 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DDB771065670
	for <freebsd-hackers@freebsd.org>; Thu, 29 Mar 2012 20:10:23 +0000 (UTC)
	(envelope-from dieterbsd@engineer.com)
Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67])
	by mx1.freebsd.org (Postfix) with SMTP id 8253B8FC14
	for <freebsd-hackers@freebsd.org>; Thu, 29 Mar 2012 20:10:23 +0000 (UTC)
Received: (qmail 995 invoked by uid 0); 29 Mar 2012 19:17:37 -0000
Received: from 67.206.186.239 by rms-us012.v300.gmx.net with HTTP
Content-Type: text/plain; charset="utf-8"
Date: Thu, 29 Mar 2012 15:17:34 -0400
From: "Dieter BSD" <dieterbsd@engineer.com>
Message-ID: <20120329191735.155070@gmx.com>
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
X-Authenticated: #74169980
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
Content-Transfer-Encoding: 8bit
X-GMX-UID: GNAGb/dd3zOlNR3dAHAhrbh+IGRvb0BN
Subject: mlock(2) man page errata
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 20:10:23 -0000

mlock(2) says:

> A single process can mlock() the minimum of a system-wide
> ``wired pages'' limit and the per-process RLIMIT_MEMLOCK
> resource limit.

Shouldn't this say maximum rather than minimum?

> [EAGAIN] Locking the indicated range would exceed either the
> system or per-process limit for locked memory.
>
> [ENOMEM] Some portion of the indicated address range is not
> allocated. There was an error faulting/mapping a page.

In some cases, the code returns ENOMEM if the limit is exceeded.