From owner-freebsd-questions@FreeBSD.ORG Sat Apr 12 18:55:03 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E736106566C for ; Sat, 12 Apr 2008 18:55:03 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 994E68FC18 for ; Sat, 12 Apr 2008 18:55:02 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl44-27.kln.forthnet.gr [77.49.171.27]) (authenticated bits=128) by igloo.linux.gr (8.14.2/8.14.2/Debian-3) with ESMTP id m3CIsjxb031591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 12 Apr 2008 21:54:52 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m3CIshBS002480; Sat, 12 Apr 2008 21:54:43 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m3CIseeP002479; Sat, 12 Apr 2008 21:54:40 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: freebsd@sopwith.solgatos.com References: <200804121515.PAA01187@sopwith.solgatos.com> Date: Sat, 12 Apr 2008 21:54:40 +0300 In-Reply-To: <200804121515.PAA01187@sopwith.solgatos.com> (Dieter's message of "Sat, 12 Apr 2008 08:15:41 +0100") Message-ID: <87ej9aaopb.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m3CIsjxb031591 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.911, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.49, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-questions@freebsd.org Subject: Re: 6.2 -> 7.0 now mlock(2) fails X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2008 18:55:03 -0000 On Sat, 12 Apr 2008 08:15:41 +0100, Dieter wrote: > I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes > get mlock(2) failed: Resource temporarily unavailable. That's error EAGAIN: [EAGAIN] Locking the indicated range would exceed either the system or per-process limit for locked memory. You are hitting either the `vm.max_wired' limit, or the per-process RLIMIT_MEMLOCK limit. > What changed and how do I fix it? It would be nice if you could run a test program that prints the value of vm.max_wired and RLIMIT_MEMLOCK on 6.2 and then on 7.0. As an extra test, it may be worth printing these values in the log of your application when mlock(2) fails.