public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Adam Litke'" <agl@us.ibm.com>, <linux-kernel@vger.kernel.org>
Cc: <ak@suse.de>, <christoph@lameter.com>, <dwg@au1.ibm.com>
Subject: RE: [RFC] Demand faulting for large pages
Date: Fri, 5 Aug 2005 15:05:39 -0700	[thread overview]
Message-ID: <200508052205.j75M5gg32259@unix-os.sc.intel.com> (raw)
In-Reply-To: <200508052133.j75LXig31835@unix-os.sc.intel.com>

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.   

Chen, Kenneth W wrote on Friday, August 05, 2005 2:34 PM
> Spurious WARN_ON.  Calls to hugetlb_pte_fault() is conditioned upon 
> if (is_vm_hugetlb_page(vma))
> 
> ....
> 
> Broken here.  Return VM_FAULT_SIGBUS when *pte is present??  Why
> can't you move all the logic into hugetlb_pte_fault and simply call
> it directly from handle_mm_fault?


I'm wondering has this patch ever been tested?  More broken bits:
in arch/i386/mm/hugetlbpage.c:huge_pte_offset - with demand paging,
you can't unconditionally walk the page table without checking
existence of pud and pmd.

I haven't looked closely at recent change in free_pgtables(), but
we used to have a need to scrub old pmd mapping before allocate one
for hugetlb pte on x86.  You have to do that in huge_pte_alloc(),
I'm specifically concerned with arch/i386/mm/hugetlbpage.c:huge_pte_alloc()

- Ken


  reply	other threads:[~2005-08-05 22:08 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
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 [this message]
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=200508052205.j75M5gg32259@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=agl@us.ibm.com \
    --cc=ak@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox