From: Christoph Hellwig <hch@infradead.org>
To: Adam Litke <agl@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: Wed, 10 May 2006 21:49:28 +0100 [thread overview]
Message-ID: <20060510204928.GA31315@infradead.org> (raw)
In-Reply-To: <1147293156.24029.95.camel@localhost.localdomain>
On Wed, May 10, 2006 at 03:32:36PM -0500, Adam Litke wrote:
> By smart fallback do you mean we should convert the hugetlb fault code
> back to using VM_FAULT_SIGBUS and writing userspace sighandlers to do
> the same thing I am, but in userspace? FWIW I did implement that in
> libhugetlbfs to try it out, but that seems much dirtier to me than
> handling faults in the kernel.
Umm, why do these faults happen at all? When all the hugetlb code went
in it we allocated at mmap time. Later it was converted to demand faulting
but under the premise that we keep the strict overcommit accounting. When
did that part go away aswell? With strict overcommit handling for huge
pages no fault should happen when the pool is exausted.
next prev parent reply other threads:[~2006-05-10 20:49 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 [this message]
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
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=20060510204928.GA31315@infradead.org \
--to=hch@infradead.org \
--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