From owner-freebsd-current@FreeBSD.ORG Thu Jul 5 22:23:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BF5D106564A for ; Thu, 5 Jul 2012 22:23:51 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id E4AEF8FC19 for ; Thu, 5 Jul 2012 22:23:50 +0000 (UTC) Received: from server.rulingia.com (c220-239-248-69.belrs5.nsw.optusnet.com.au [220.239.248.69]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q65MNnCw036775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 6 Jul 2012 08:23:50 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q65MNi9q086174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 6 Jul 2012 08:23:44 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q65MNi1L086173 for freebsd-current@freebsd.org; Fri, 6 Jul 2012 08:23:44 +1000 (EST) (envelope-from peter) Date: Fri, 6 Jul 2012 08:23:44 +1000 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20120705222344.GC85696@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YD3LsXFS42OYHhNZ" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Subject: RAM fragmention problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 05 Jul 2012 22:23:51 -0000 --YD3LsXFS42OYHhNZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am running into a problem with RAM fragmentation causing contigmalloc() failures and wonder if anyone has a tool that that would allow me to identify the owner(s) of pages of RAM within a region on amd64. --=20 Peter Jeremy --YD3LsXFS42OYHhNZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/2E/AACgkQ/opHv/APuIelogCfVTuKYo3djzxuhaMrebs/xLLP +T8An0yNPVXTpD+Br3JqANh/Q6hV4Zl7 =a0sb -----END PGP SIGNATURE----- --YD3LsXFS42OYHhNZ--