From: Andi Kleen <ak@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Adam Litke'" <agl@us.ibm.com>,
linux-kernel@vger.kernel.org, ak@suse.de, christoph@lameter.com,
dwg@au1.ibm.com
Subject: Re: [RFC] Demand faulting for large pages
Date: Fri, 5 Aug 2005 23:35:45 +0200 [thread overview]
Message-ID: <20050805213545.GB8266@wotan.suse.de> (raw)
In-Reply-To: <200508052105.j75L5jg31470@unix-os.sc.intel.com>
On Fri, Aug 05, 2005 at 02:05:42PM -0700, Chen, Kenneth W wrote:
> Adam Litke wrote on Friday, August 05, 2005 8:22 AM
> > Below is a patch to implement demand faulting for huge pages. The main
> > motivation for changing from prefaulting to demand faulting is so that
> > huge page allocations can follow the NUMA API. Currently, huge pages
> > are allocated round-robin from all NUMA nodes.
>
> Do users of hugetlb going to accept the fact that now app will SIGBUS
> when there aren't enough free hugetlb pages present at the time of fault?
> It's not very nice though, but is that the general consensus?
Probably not. But the simple minded overcommit check at mapping that was in the
earlier SLES codebase seemed to work for people (or at least I've never
heard a complaint about that). Adding that should be pretty easy.
-Andi
next prev parent reply other threads:[~2005-08-05 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 15:21 Adam Litke
2005-08-05 15:53 ` Andi Kleen
2005-08-05 16:37 ` Adam Litke
2005-08-05 16:47 ` Andi Kleen
2005-08-05 17:00 ` Adam Litke
2005-08-05 17:12 ` Andi Kleen
2005-08-05 17:09 ` Christoph Lameter
2005-08-05 21:05 ` Chen, Kenneth W
2005-08-05 21:35 ` Andi Kleen [this message]
2005-08-05 21:33 ` Chen, Kenneth W
2005-08-05 22:05 ` Chen, Kenneth W
2005-08-08 22:16 ` Adam Litke
2005-08-08 22:36 ` Chen, Kenneth W
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=20050805213545.GB8266@wotan.suse.de \
--to=ak@suse.de \
--cc=agl@us.ibm.com \
--cc=christoph@lameter.com \
--cc=dwg@au1.ibm.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®