From: Christoph Lameter <christoph@engr.sgi.com>
To: Adam Litke <agl@us.ibm.com>
Cc: linux-mm@kvack.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: Wed, 10 May 2006 16:42:01 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605101633140.7639@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1147287400.24029.81.camel@localhost.localdomain>
Seems that the code is not modifying x86 code but all code.
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?
--
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>
next parent reply other threads:[~2006-05-10 23:44 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 [this message]
[not found] ` <1147363859.24029.134.camel@localhost.localdomain>
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=Pine.LNX.4.64.0605101633140.7639@schroedinger.engr.sgi.com \
--to=christoph@engr.sgi.com \
--cc=agl@us.ibm.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