From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ed Sweetman <safemode@comcast.net>
Cc: Jens Axboe <axboe@suse.de>,
Jan-Frode Myklebust <janfrode@parallab.uib.no>,
linux-kernel@vger.kernel.org
Subject: Re: OOM-killer going crazy.
Date: Wed, 28 Jul 2004 11:00:27 +1000 [thread overview]
Message-ID: <4106FAAB.5080106@yahoo.com.au> (raw)
In-Reply-To: <4106D978.7090008@comcast.net>
Ed Sweetman wrote:
> Nick Piggin wrote:
>
>> OK so it does sound like a different problem.
>>
>> I didn't follow your other thread closely... does /proc/slabinfo
>> show any evidence of a leak?
>
>
>
> Surprisingly no. You'd think that since the kernel is responsible for
> saying what memory can't be touched or swapped out it would have some
> sort of tag on the huge 600MB of ram I currently can't do anything with
> since i burned that audio cd but slabinfo doesn't seem to show anything
> about it. Maybe i'm reading it wrong.
>
It could be memory coming straight out of the page allocator that
isn't being freed.
Jens, any ideas?
next prev parent reply other threads:[~2004-07-28 1:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 9:46 memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) Eduard Bloch
2004-07-26 1:30 ` Ed Sweetman
2004-07-26 9:10 ` OOM-killer going crazy. (was: Re: memory not released after using cdrecord/cdrdao) Jan-Frode Myklebust
2004-07-26 10:55 ` Nick Piggin
2004-07-26 11:10 ` Jan-Frode Myklebust
2004-07-26 11:43 ` OOM-killer going crazy Nick Piggin
2004-07-26 12:46 ` Jan-Frode Myklebust
2004-07-27 1:00 ` Nick Piggin
2004-07-26 13:02 ` Ed Sweetman
2004-07-27 4:19 ` Nick Piggin
2004-07-27 10:07 ` Jens Axboe
2004-07-27 13:23 ` Ed Sweetman
2004-07-27 13:30 ` Nick Piggin
2004-07-27 22:38 ` Ed Sweetman
2004-07-28 1:00 ` Nick Piggin [this message]
2004-07-28 6:30 ` Ed Sweetman
2004-07-28 6:45 ` Jens Axboe
2004-07-28 12:58 ` Ed Sweetman
2004-07-28 13:31 ` Jens Axboe
2004-07-29 0:08 ` memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) William Lee Irwin III
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=4106FAAB.5080106@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=axboe@suse.de \
--cc=janfrode@parallab.uib.no \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@comcast.net \
/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