linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Adam Litke <agl@us.ibm.com>
To: linux-mm@kvack.org
Subject: [RFC] Hugetlb fallback to normal pages
Date: Wed, 26 Apr 2006 14:46:20 -0500	[thread overview]
Message-ID: <1146080780.3872.69.camel@localhost.localdomain> (raw)

Thanks to the latest hugetlb accounting patches, we now have reliable
shared mappings.  Private mappings are much more difficult because there
is no way to know up-front how many huge pages will be required (we may
have forking combined with unknown copy-on-write activity).  So private
mappings currently get full overcommit semantics and when a fault cannot
be handled, the apps get SIGBUS.

The problem: Random SIGBUS crashes for applications using large pages
are not acceptable.  We need a way to handle the fault without giving up
and killing the process.

So I've been mulling it over and as I see it, we either 1) Swap out huge
pages, or 2) Demote huge pages.  In either case we need to be willing to
accept the performance penalty to gain stability.  At this point, I
think swapping is too intrusive and way too slow so I am considering
demotion options.  To simplify things at first, I am only considering
i386 (and demoting only private mappings of course).

Here's my idea:  When we fail to instantiate a new page at fault time,
split the affected vma such that we have a new vma to cover the 1 huge
page we are demoting.  Allocate HPAGE_SIZE/PAGE_SIZE normal pages.  Use
the page table to locate any populated hugetlb pages.  Copy the data
into the normal pages and install them in the page table.  Do any other
fixup required to make the new VMA anonymous.  Return.

Any general opinions on the idea (flame retardant suit is equipped)?  As
far as I can tell, we don't split vmas during fault anywhere else.  Is
there inherent problems with doing so?  What about the conversion
process to an anonymous VMA?  Since we are dealing with private mappings
only, divorcing the vma from the hugetlbfs file should be okay afaics.

I know code speaks louder than words, but talk is cheap and that's why
I'm starting with it :)  Thanks for your comments.

-- 
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center

--
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>

             reply	other threads:[~2006-04-26 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 19:46 Adam Litke [this message]
2006-04-27 23:31 ` [RFC] Hugetlb fallback to normal pages Chen, Kenneth W
2006-05-01 15:46   ` Dave Hansen
2006-05-01 16:23     ` 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=1146080780.3872.69.camel@localhost.localdomain \
    --to=agl@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).