All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: OOM-killer too aggressive?
Date: Sun, 26 Feb 2006 12:39:31 -0600	[thread overview]
Message-ID: <4401F5E3.3090003@shaw.ca> (raw)
In-Reply-To: <5KvnZ-4uN-27@gated-at.bofh.it>

Chuck Ebbert wrote:
> DMA free:44kB min:32kB low:40kB high:48kB active:0kB inactive:0kB
> present:15728kB pages_scanned:0 all_unreclaimable? yes

I think the big question is who used up all the DMA zone.. Surely not 
the floppy driver..

> So it will try to allocate half its first request if that fails, then
> fall back to non-DMA memory as a last resort, but doesn't get a chance
> because the OOM killer gets invoked.  Maybe we need a new flag that says
> "fail me immediately if no memory available"?

I think __GFP_NORETRY already does this.. There is also __GFP_NOWARN 
which suppresses the allocation failure warning, not sure if we want 
that or not..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-02-26 18:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5KvnZ-4uN-27@gated-at.bofh.it>
2006-02-26 18:39 ` Robert Hancock [this message]
2006-02-26 21:56   ` OOM-killer too aggressive? Marcelo Tosatti
2006-02-26 20:56     ` Chris Largret
2006-02-27  0:22       ` Marcelo Tosatti
2006-02-27  1:48         ` Chris Largret
2006-02-27 15:47           ` Marcelo Tosatti
2006-02-26 23:32 Chuck Ebbert
  -- strict thread matches above, loose matches on Subject: below --
2006-02-26 14:35 Chuck Ebbert
2006-02-26 18:21 ` Andrew Morton
2006-02-26 20:39   ` Andi Kleen
2006-02-26 21:04     ` Andrew Morton
2006-02-26 21:06   ` Chris Largret
2006-02-26 21:31     ` Andrew Morton
2006-02-26 23:00       ` Chris Largret
2006-02-27  0:20         ` Andrew Morton
2006-02-27  1:01           ` Chris Largret
2006-02-27  1:57             ` Andrew Morton
2006-02-27  6:34               ` Chris Largret
2006-02-26 23:47       ` Andi Kleen
2006-02-26 23:51       ` Andi Kleen
2006-02-27 22:30         ` Christoph Lameter
2006-02-28  0:41           ` Andi Kleen
2006-02-28  0:59             ` Andrew Morton
2006-02-28  1:03               ` Christoph Lameter
2006-02-28  1:25               ` Andi Kleen
2006-02-28  1:38                 ` Andrew Morton
2006-02-28 12:09                   ` Andi Kleen

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=4401F5E3.3090003@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=76306.1226@compuserve.com \
    --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.