Date: Thu, 24 Jun 2004 13:55:41 -0300
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: William Lee Irwin III <wli@holomorphy.com>, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org
Subject: Re: [oom]: [0/4] fix OOM deadlock running OAST
Message-ID: <20040624165541.GA21496@logos.cnet>
References: <20040623151659.70333c6d.akpm@osdl.org> <20040623223146.GG1552@holomorphy.com> <20040623153758.40e3a865.akpm@osdl.org> <20040623230730.GJ1552@holomorphy.com> <20040623163819.013c8585.akpm@osdl.org> <20040624000308.GK1552@holomorphy.com> <20040623171818.39b73d52.akpm@osdl.org> <20040624002651.GL1552@holomorphy.com> <20040624141637.GA20702@logos.cnet> <20040624152301.GC21066@holomorphy.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040624152301.GC21066@holomorphy.com>
User-Agent: Mutt/1.5.5.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 748
Lines: 17

On Thu, Jun 24, 2004 at 08:23:01AM -0700, William Lee Irwin III wrote:
> On Thu, Jun 24, 2004 at 11:16:37AM -0300, Marcelo Tosatti wrote:
> > Removing the check on v2.4 based kernels will trigger the OOM killer
> > too soon for a lot of cases, I'm pretty sure.
> 
> Other 2.4 oom_kill.c issues aside, since this is a relatively blatant
> deadlock. What form would you like a fix to take, if you care to have
> a fix for this at all?

Lets hold this on 2.4.28-pre1, as discussed privately.

Thanks again.
-
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/