All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jan-Frode Myklebust <janfrode@parallab.uib.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM-killer going crazy.
Date: Tue, 27 Jul 2004 11:00:44 +1000	[thread overview]
Message-ID: <4105A93C.5030109@yahoo.com.au> (raw)
In-Reply-To: <20040726124628.GA2488@ii.uib.no>

Jan-Frode Myklebust wrote:

>On Mon, Jul 26, 2004 at 09:43:24PM +1000, Nick Piggin wrote:
>
>>Can you try echo 10000 > /proc/sys/vm/vfs_cache_pressure, and see how that 
>>goes?
>>
>
>
>Yes! Now it works. So is vfs_cache_pressure=10000 a sensible value to use? 
>
>

Well if it keeps you going then yes. For now. I'll get back to you with
something to try though.

Thanks.



  reply	other threads:[~2004-07-27  1:01 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 [this message]
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
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=4105A93C.5030109@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=janfrode@parallab.uib.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.