From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 30 01:13:56 2012 Return-Path: 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 9BFD6106564A for ; Fri, 30 Mar 2012 01:13:56 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 30C758FC0A for ; Fri, 30 Mar 2012 01:13:55 +0000 (UTC) Received: by wibhj6 with SMTP id hj6so96041wib.13 for ; Thu, 29 Mar 2012 18:13:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V5f866Fk+gy22ebK4dusBYsFrhgTVQ+iEUBMQDqpLbw=; b=oUiAKdEm2AaIW70iKoZURXrxxASY+0aBb9kjYzdRJI40I2qy9LU/H+m/P4d3/4LiRv a/rbHy8HNBTj7abPC5H09afXHhwV0tpVaeS/MKAbGtS4B28CJG6GszetnGUiuL1emW4c U7ZGsIlPLB439J2j78irqwh1PmdxtC7hDULDn7MJsDXlOzJs0YCOGHQWfnlMrF1ET0PV nY2WCBq1PabTJrL5Aa9ggDznOIwzkSEg75Jyv2CeUa9CxM18tOhCTMvPYep9HYYXSgjk NpUrkJj3xhNitYfCGGZzUKra8z5/qgVcoKPtJQokeA54K1QuVsMQhw8n4a/RmhRulpjr SMJg== MIME-Version: 1.0 Received: by 10.180.81.37 with SMTP id w5mr777295wix.16.1333070035096; Thu, 29 Mar 2012 18:13:55 -0700 (PDT) Received: by 10.180.79.137 with HTTP; Thu, 29 Mar 2012 18:13:55 -0700 (PDT) In-Reply-To: <20120329191735.155070@gmx.com> References: <20120329191735.155070@gmx.com> Date: Thu, 29 Mar 2012 21:13:55 -0400 Message-ID: From: Ryan Stone To: Dieter BSD Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2012 01:13:56 -0000 On Thu, Mar 29, 2012 at 3:17 PM, Dieter BSD wrote: > 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? I don't think so. The minimum of the two would be the limit that you will hit first, and presumably is the point at which you cannot mlock any more pages.