DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=P0xvafRSq5z2qedsWR4St+l9EuNAswb7VrQsuK/HRo14I2ZIQtLxaNXbOUkFPW4QWv+RVmt3Mi5RmIZ6v7I9ji3VEbD98QS4oGn6M+per05Df3MCyqnk69nRf59V8kFdira9amI0e4WQ9U2tdJcZcXUny1P8cYxqTwiaieO43yA=
Message-ID: <2cd57c90050427110717b6e841@mail.gmail.com>
Date: Thu, 28 Apr 2005 02:07:28 +0800
From: Coywolf Qi Hunt <coywolf@gmail.com>
Reply-To: coywolf@lovecn.org
To: Chris Friesen <cfriesen@nortel.com>
Subject: Re: any way to find out kernel memory usage?
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <426FBFED.9090409@nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <426FBFED.9090409@nortel.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1149
Lines: 34

On 4/28/05, Chris Friesen <cfriesen@nortel.com> wrote:
> 
> We recently had an issue with a kernel module leaking memory on unload,
> and a userspace app that unloaded it way too many times.
> 
> This ended up using up a bunch of memory, which triggered the oom-killer
> to run, which went wild killing everything in sight since userspace
> wasn't actually the culprt.
> 
> One idea we had to prevent this in the future is to configure the OOM
> killer to reset the system if the kernel uses more than a certain amount
> of memory.  (Reset is better than hang for our purposes.) Is there any

Curiously, how to reset? Reboot? (Teach oom killer to kill) or restart
the related
kernel thread?


> way to find out how much memory the kernel is using?  I don't see
> anything in /proc, but maybe something internal that isn't currently
> exported?
> 
> Chris


-- 
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/