From owner-freebsd-current@FreeBSD.ORG Tue May 13 11:27:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A80537B401 for ; Tue, 13 May 2003 11:27:26 -0700 (PDT) Received: from basement.kutulu.org (pcp03610121pcs.longhl01.md.comcast.net [68.49.239.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCEAF43FA3 for ; Tue, 13 May 2003 11:27:25 -0700 (PDT) (envelope-from kutulu@kutulu.org) Received: by basement.kutulu.org (Postfix, from userid 1001) id CF635A946; Tue, 13 May 2003 14:27:38 -0400 (EDT) Date: Tue, 13 May 2003 14:27:38 -0400 From: Michael Edenfield To: current@freebsd.org Message-ID: <20030513182738.GA17766@basement.kutulu.org> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Mailer: Mutt http://www.mutt.org/ X-Accept-Language: en X-PGP-Key: http://www.kutulu.org/pgp/kutulu.asc X-PGP-Fingerprint: 1CE0 3C31 7013 D529 406D 37DC 09CC CD84 A46C 878F Subject: vm_page_max_wired and gpg... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 18:27:26 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable For some time now, gpg has been having issues on my -CURRENT system=20 with being unable to mlock() the ~8k buffer it uses to hold the=20 decrypted secret key. A ktrace shows that it's being returned an=20 EAGAIN from mlock(), which my peeking around has shown could be: 1) I hit the RLIMIT_MLOCK limit on memory locking, or 2) I hit the system-wide "wired pages" limit. There are no memlock resource limits, so I figure it must be #2. I=20 have managed to figure out that the limit in question is held in=20 "vm_page_max_wired" in vm_pageout.c, but I can't find any way to=20 display this number at runtime. =20 I have (I think) plenty of RAM on this machine, certainly enough for=20 gpg to lock 8k of it for a few seconds, so I dunno why I'd be hitting=20 any system-wide limit. =20 Any advice on where to look further? --Mike --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+wTkZCczNhKRsh48RAmDgAJ9JPTyHSPbvdBveRqxvYbmvPce/ywCeLqzP t7ncqgYgvsTDLI6+O5lXZUU= =VmLH -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--