From: Andi Kleen <ak@suse.de>
To: Adam Litke <agl@us.ibm.com>
Cc: 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 17:53:07 +0200 [thread overview]
Message-ID: <20050805155307.GV8266@wotan.suse.de> (raw)
In-Reply-To: <1123255298.3121.46.camel@localhost.localdomain>
On Fri, Aug 05, 2005 at 10:21:38AM -0500, Adam Litke wrote:
> 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.
I think matching DEFAULT is better than having a different default for
huge pages than for small pages.
In general more programs are happy with local memory than remote memory.
Also it makes it consistent.
>
> The default behavior in SLES9 for i386 is to use demand faulting with
> NUMA policy-aware allocations. To my knowledge, this continues to work
Not sure what you're trying to say here. All allocations are NUMA policy aware.
> well in practice. Thanks to consolidated hugetlb code, switching the
> behavior requires changing only one fault handler. The bulk of the
> patch just moves the logic from hugelb_prefault() to
> hugetlb_pte_fault().
Are you sure you fixed get_user_pages to handle this properly? It doesn't
like it.
-Andi
next prev parent reply other threads:[~2005-08-05 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 15:21 [RFC] Demand faulting for large pages Adam Litke
2005-08-05 15:53 ` Andi Kleen [this message]
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
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=20050805155307.GV8266@wotan.suse.de \
--to=ak@suse.de \
--cc=agl@us.ibm.com \
--cc=christoph@lameter.com \
--cc=dwg@au1.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.