From: Adam Litke <agl@us.ibm.com>
To: Christoph Lameter <christoph@engr.sgi.com>
Cc: linux-mm@kvack.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: Thu, 11 May 2006 11:10:58 -0500 [thread overview]
Message-ID: <1147363859.24029.134.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0605101633140.7639@schroedinger.engr.sgi.com>
On Wed, 2006-05-10 at 16:42 -0700, Christoph Lameter wrote:
> Seems that the code is not modifying x86 code but all code.
Right. It's definitely broken in that regard. I sent it out in this
condition so the patch was small, easy to review, and my approach would
be easy to see.
> An app should be getting an out of memory error and not a SIGBUS when
> running out of memory.
>
> I thought we fixed the SIGBUS problems and were now reporting out of
> memory? If there still is an issue then we better fix out of memory
> handling. Provide a way for the app to trap OOM conditions?
Yes, the SIGBUS issues are "fixed". Now the application is killed
directly via VM_FAULT_OOM so it is not possible to handle the fault from
userspace. For my libhugetlbfs-based fallback approach, I needed to
patch the kernel so that SIGBUS was delivered to the process like in the
days of old.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
next prev parent reply other threads:[~2006-05-11 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 18:56 [RFC] Hugetlb demotion for x86 Adam Litke
2006-05-10 19:46 ` Dave Hansen
2006-05-10 19:49 ` Dave Hansen
2006-05-10 20:05 ` Christoph Hellwig
2006-05-10 20:32 ` Adam Litke
2006-05-10 20:49 ` Christoph Hellwig
2006-05-10 21:45 ` Adam Litke
2006-05-11 15:15 ` Hugh Dickins
2006-05-11 15:33 ` Alan Cox
2006-05-11 15:59 ` Adam Litke
2006-05-10 21:38 ` Andi Kleen
2006-05-10 23:42 ` Christoph Lameter
2006-05-11 16:10 ` Adam Litke [this message]
2006-05-15 14:20 ` Dave Hansen
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=1147363859.24029.134.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=christoph@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox