linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Adam Litke <agl@us.ibm.com>
Cc: Christoph Lameter <christoph@engr.sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: Mon, 15 May 2006 07:20:17 -0700	[thread overview]
Message-ID: <1147702817.6623.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1147363859.24029.134.camel@localhost.localdomain>

On Thu, 2006-05-11 at 11:10 -0500, Adam Litke wrote:
> 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.

Maybe this could be off-by-default behavior that can be enabled with a
special mmap flag or madvise, or something similar.  It seems that apps
don't want to get SIGBUS for low memory.  But, if they have _asked_ for
it, perhaps they'd be a bit more willing.

(BTW, I fixed the bogus linux-mm cc, finally ;)

-- Dave

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2006-05-15 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1147287400.24029.81.camel@localhost.localdomain>
2006-05-10 23:42 ` Christoph Lameter
     [not found]   ` <1147363859.24029.134.camel@localhost.localdomain>
2006-05-15 14:20     ` Dave Hansen [this message]

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=1147702817.6623.27.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=christoph@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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