public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jon 'tex' Boone" <tex@delamancha.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>, <kernelnewbies@nl.linux.org>
Subject: Re: WANTED: Re: VM lockup with 2.4.8 / 2.4.8pre8
Date: Tue, 14 Aug 2001 15:04:59 -0400	[thread overview]
Message-ID: <m38zgmpin8.fsf@amicus.delamancha.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108131451470.6118-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0108131451470.6118-100000@imladris.rielhome.conectiva> (Rik van Riel's message of "Mon, 13 Aug 2001 14:55:42 -0300 (BRST)")

Rik van Riel <riel@conectiva.com.br> writes:

> CALL FOR VOLUNTEERS
> ---------------------
> This means the OOM killer should be tuned, or more precisely,
> the code deciding when the OOM killer kicks in should be tuned.
> 
> The code involved is very easy, so I'll explain it a bit and
> ask for volunteers to tweak the code and fix the OOM behaviour.
> 
> The functions/places you may want to tweak are:
> 
> mm/vmscan.c::kswapd()
> 	else if (out_of_memory()) {
> 		oom_kill()
> 
> mm/oom_kill.c::out_of_memory()

Rik,

    Should said volunteer(s) work with stock 2.4.8?

-tex
-- 
------------------
Jon Allen Boone
tex@delamancha.org

  reply	other threads:[~2001-08-14 19:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 17:47 VM lockup with 2.4.8 / 2.4.8pre8 Roy C. Bixler
2001-08-13 17:55 ` WANTED: " Rik van Riel
2001-08-14 19:04   ` Jon 'tex' Boone [this message]
2001-08-14 19:32     ` Rik van Riel
2001-08-14 20:05   ` Petr Baudis
2001-08-14 20:27     ` Rik van Riel
     [not found]   ` <9lc0ek$l5k$1@ns1.clouddancer.com>
2001-08-15 19:35     ` Colonel
2001-08-15 20:14       ` Admin Mailing Lists
2001-08-15 20:51       ` David Ford
     [not found]       ` <9lelsk$bri$1@ns1.clouddancer.com>
2001-08-16  4:27         ` Colonel
2001-08-16  9:27           ` Marco Colombo
2001-08-14 19:13 ` Roy C. Bixler

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=m38zgmpin8.fsf@amicus.delamancha.org \
    --to=tex@delamancha.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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