public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any way to find out kernel memory usage?
Date: Thu, 28 Apr 2005 02:07:28 +0800	[thread overview]
Message-ID: <2cd57c90050427110717b6e841@mail.gmail.com> (raw)
In-Reply-To: <426FBFED.9090409@nortel.com>

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/

  parent reply	other threads:[~2005-04-27 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 16:38 any way to find out kernel memory usage? Chris Friesen
2005-04-27 16:42 ` Artem B. Bityuckiy
2005-04-27 16:57   ` Chris Friesen
2005-04-27 17:20     ` Robert Love
2005-04-27 17:44       ` Chris Friesen
2005-04-27 17:47         ` Robert Love
2005-04-27 22:23           ` Mark Lord
2005-04-27 18:07 ` Coywolf Qi Hunt [this message]
2005-04-27 18:29   ` Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cd57c90050427110717b6e841@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=cfriesen@nortel.com \
    --cc=coywolf@lovecn.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox