From: Adam Litke <agl@us.ibm.com>
To: akpm@osdl.org
Cc: "ADAM G. LITKE [imap]" <agl@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/3] Demand faulting for huge pages
Date: Wed, 28 Sep 2005 15:25:41 -0500 [thread overview]
Message-ID: <1127939141.26401.32.camel@localhost.localdomain> (raw)
Hi Andrew. Can we give hugetlb demand faulting a spin in the mm tree?
And could people with alpha, sparc, and ia64 machines give them a good
spin? I haven't been able to test those arches yet.
-Thanks
- htlb-get_user_pages removes an optimization that is no longer valid
when demand faulting huge pages
- htlb-fault moves the fault logic from hugetlb_prefault() to
hugetlb_pte_fault() and find_get_huge_page().
- htlb-acct adds an overcommit check to maintain the no-overcommit
semantics provided by hugetlb_prefault()
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Adam Litke <agl@us.ibm.com>
To: akpm@osdl.org
Cc: "ADAM G. LITKE [imap]" <agl@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/3] Demand faulting for huge pages
Date: Wed, 28 Sep 2005 15:25:41 -0500 [thread overview]
Message-ID: <1127939141.26401.32.camel@localhost.localdomain> (raw)
Hi Andrew. Can we give hugetlb demand faulting a spin in the mm tree?
And could people with alpha, sparc, and ia64 machines give them a good
spin? I haven't been able to test those arches yet.
-Thanks
- htlb-get_user_pages removes an optimization that is no longer valid
when demand faulting huge pages
- htlb-fault moves the fault logic from hugetlb_prefault() to
hugetlb_pte_fault() and find_get_huge_page().
- htlb-acct adds an overcommit check to maintain the no-overcommit
semantics provided by hugetlb_prefault()
--
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>
next reply other threads:[~2005-09-28 20:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 20:25 Adam Litke [this message]
2005-09-28 20:25 ` [PATCH 0/3] Demand faulting for huge pages Adam Litke
2005-09-28 20:31 ` [PATCH 1/3 htlb-get_user_pages] " Adam Litke
2005-09-28 20:31 ` Adam Litke
2005-09-28 20:32 ` [PATCH 2/3 htlb-fault] " Adam Litke
2005-09-28 20:32 ` Adam Litke
2005-09-29 6:09 ` Andrew Morton
2005-09-29 6:09 ` Andrew Morton
2005-09-29 6:10 ` Andrew Morton
2005-09-29 6:10 ` Andrew Morton
2005-09-28 20:33 ` [PATCH 3/3 htlb-acct] " Adam Litke
2005-09-28 20:33 ` Adam Litke
2005-09-29 6:20 ` Andrew Morton
2005-09-29 6:20 ` Andrew Morton
2005-09-29 9:45 ` Andi Kleen
2005-09-29 9:45 ` Andi Kleen
2005-09-29 13:40 ` [NUMA , x86_64] Why memnode_shift is chosen with the lowest possible value ? Eric Dumazet
2005-09-29 13:43 ` Andi Kleen
2005-09-29 16:59 ` Eric Dumazet
2005-09-30 9:09 ` Eric Dumazet
2005-10-04 17:13 ` Andi Kleen
2005-10-04 21:12 ` Eric Dumazet
2005-09-29 13:32 ` [PATCH 0/3] Demand faulting for huge pages Hugh Dickins
2005-09-29 13:32 ` Hugh Dickins
2005-10-06 15:22 ` Adam Litke
2005-10-06 15:22 ` Adam Litke
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=1127939141.26401.32.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.