public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: AChittenden@bluearc.com, linux-kernel@vger.kernel.org,
	lwoodman@redhat.com
Subject: Re: Out of Memory: Killed process 16498 (java).
Date: Thu, 19 Jan 2006 20:28:44 -0500	[thread overview]
Message-ID: <20060120012844.GE3798@redhat.com> (raw)
In-Reply-To: <20060119170305.2e8ae353.akpm@osdl.org>

On Thu, Jan 19, 2006 at 05:03:05PM -0800, Andrew Morton wrote:
 > This is the bypass-the-batching patch.  It's a reasonable thing to do, but I'd
 > just do it unconditionally and remove the code which clears
 > ->all_unreclaimable from free_pages_bulk(), if possible.
 > 
 > Has this patch been shown to have any effect?  If so, what was it, and
 > under what conditions?

Larry originally came up with the patch for our RHEL4 2.6.9 kernel,
after customers were hitting OOM under some heavy workload he can
probably recall better than I can.

iirc it didn't solve the users OOM entirely, but it does make their workload
run longer before the kill happens.

A little while later, after Fedora users started reporting oom kills,
I forward-ported it to 2.6.14, and threw it out in an update.
The Fedora user in the bug report
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175173
who on x86-64 with 5GB saw zone_dma exhausted saw a similar result,
delays the kill, but it does still happen.

Hmm.

		Dave

  reply	other threads:[~2006-01-20  1:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 15:11 Out of Memory: Killed process 16498 (java) Andy Chittenden
2006-01-19 19:48 ` Dave Jones
2006-01-19 22:15   ` Andrew Morton
2006-01-20  8:12     ` Jens Axboe
2006-01-20  8:23       ` Andrew Morton
2006-01-20 12:08         ` Jens Axboe
2006-01-20 12:17           ` Andrew Morton
2006-01-20 12:28             ` Jens Axboe
2006-01-20 12:51               ` Andrew Morton
2006-01-20  1:03   ` Andrew Morton
2006-01-20  1:28     ` Dave Jones [this message]
2006-01-20  1:49       ` Andrew Morton
2006-01-21 20:00         ` Dan Aloni
  -- strict thread matches above, loose matches on Subject: below --
2006-01-27 11:53 Andy Chittenden
2006-01-27 14:21 ` Jens Axboe
2006-01-27 14:39   ` Anton Altaparmakov
2006-01-23 10:03 Andy Chittenden
2006-01-23 10:11 ` Jens Axboe
2006-01-21 21:47 Andy Chittenden
2006-01-23  9:27 ` Jens Axboe
     [not found] <89E85E0168AD994693B574C80EDB9C27035561DE@uk-email.terastack.bluearc.com>
2006-01-20 17:39 ` Jens Axboe
     [not found] <89E85E0168AD994693B574C80EDB9C27035560E4@uk-email.terastack.bluearc.com>
2006-01-20 12:37 ` Larry Woodman
     [not found] <89E85E0168AD994693B574C80EDB9C2703555F8E@uk-email.terastack.bluearc.com>
2006-01-19  9:44 ` Andrew Morton
2006-01-19  9:40 Andy Chittenden
2006-01-19  9:41 ` Con Kolivas
2006-01-19  8:43 Andy Chittenden
2006-01-19  8:56 ` Andrew Morton
2006-01-19  9:36   ` Con Kolivas
2006-01-19 20:54 ` Martin Bligh

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=20060120012844.GE3798@redhat.com \
    --to=davej@redhat.com \
    --cc=AChittenden@bluearc.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@redhat.com \
    /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