From owner-freebsd-stable Thu Jun 3 9:43: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from frolic.no-support.loc (ppp39-9.hrz.uni-bielefeld.de [129.70.39.9]) by hub.freebsd.org (Postfix) with ESMTP id C3C1B14EA4 for ; Thu, 3 Jun 1999 09:42:34 -0700 (PDT) (envelope-from bfischer@Techfak.Uni-Bielefeld.DE) Received: from broccoli.no-support.loc (broccoli.no-support.loc [192.168.43.99]) by frolic.no-support.loc (8.9.3/8.9.3) with ESMTP id SAA00889 for ; Thu, 3 Jun 1999 18:42:05 +0200 (CEST) (envelope-from bjoern@no-support.loc) From: Bjoern Fischer Received: (from bjoern@localhost) by broccoli.no-support.loc (8.9.3/8.9.3) id SAA00357 for freebsd-stable@FreeBSD.ORG; Thu, 3 Jun 1999 18:42:05 +0200 (CEST) (envelope-from bjoern@no-support.loc) Date: Thu, 3 Jun 1999 18:42:04 +0200 To: freebsd-stable@FreeBSD.ORG Subject: kldunload & wired mem Message-ID: <19990603184204.A292@broccoli.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, could it be true that wired memory that was allocated while loading a kernel module is not freed when it is unloaded again? New memory gets wired on every load/unload cycle of the same module. E.g. if you load/unload cd9660.ko repeatedly, more and more memory gets wired and the machine will reboot, when there's no memory available any more. Are there plans to improve this behavoir? At the moment I can't see any benefit from unloading a module at all. Thanks. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L+++(--) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message