public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: OOM behavior in constrained memory situations
Date: Mon, 6 Feb 2006 22:22:28 +0100	[thread overview]
Message-ID: <200602062222.28630.ak@suse.de> (raw)
In-Reply-To: <20060206131026.53dbd8d5.akpm@osdl.org>

On Monday 06 February 2006 22:10, Andrew Morton wrote:

> Do we really want to kill the application?  A more convetional response
> would be to return NULL from the page allocator and let that trickle back.

Yes that is what it's supposed to be doing.
 
> The hugepage thing is special, because it's a pagefault, not a syscall.

At least remnants from my old 80% hack to avoid this (huge_page_needed)
seem to be still there in mainline:

fs/hugetlbfs/inode.c:hugetlbfs_file_mmap

   bytes = huge_pages_needed(mapping, vma);
   if (!is_hugepage_mem_enough(bytes))
          return -ENOMEM;


So something must be broken if this doesn't work. Or did you allocate
the pages in some other way? 

>From taking a quick look at ipc/shm.c it might be missing an equivalent 
check when allocating a huge page segment.

-Andi

  reply	other threads:[~2006-02-06 21:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 20:59 OOM behavior in constrained memory situations Christoph Lameter
2006-02-06 21:10 ` Andrew Morton
2006-02-06 21:22   ` Andi Kleen [this message]
2006-02-06 22:16     ` Christoph Lameter
2006-02-06 22:25       ` Andi Kleen
2006-02-06 22:30       ` Andrew Morton
2006-02-07  0:03         ` Christoph Lameter
2006-02-09 23:08           ` David Gibson
2006-02-06 22:11   ` Christoph Lameter
2006-02-06 22:26     ` Andrew Morton
2006-02-06 22:59 ` Paul Jackson
2006-02-07  0:39   ` Christoph Lameter
2006-02-07  1:55   ` Christoph Lameter
2006-02-07  9:23     ` Andi Kleen
2006-02-07 17:29       ` Christoph Lameter
2006-02-07 17:45         ` Andi Kleen
2006-02-07 17:51           ` Christoph Lameter
2006-02-07 17:58             ` Andi Kleen
2006-02-07 18:10               ` Christoph Lameter
2006-02-07 18:19               ` Christoph Lameter
2006-02-07 18:31                 ` Andi Kleen
2006-02-07 19:00                   ` Christoph Lameter

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=200602062222.28630.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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