From: Adam Litke <agl@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: agl@us.ibm.com
Subject: [UPDATE] [PATCH 0/3] Demand faulting for hugetlb
Date: Thu, 08 Sep 2005 16:15:45 -0500 [thread overview]
Message-ID: <1126214145.28895.13.camel@localhost.localdomain> (raw)
Sending this out again after incorporating the feedback from Yanmin
Zhang and Dave Hansen. Are we ready to go for -mm yet? The only patch
which has seen any recent changes is #2 below so I assume people agree
with #1 and #3 now :)
The three patches:
1) Remove a get_user_pages() optimization that is no longer valid for
demand faulting
2) Move fault logic from hugetlb_prefault() to hugetlb_pte_fault()
3) Apply a simple overcommit check so demand fault accounting behaves
in a manner in line with how prefault worked
Diffed against 2.6.13-git6
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
next reply other threads:[~2005-09-08 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 21:15 Adam Litke [this message]
2005-09-08 21:18 ` [PATCH 1/3 htlb-get_user_pages] Demand faulting for hugetlb Adam Litke
2005-09-08 21:20 ` [PATCH 2/3 htlb-fault] " Adam Litke
2005-09-08 21:21 ` [PATCH 3/3 htlb-acct] " 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=1126214145.28895.13.camel@localhost.localdomain \
--to=agl@us.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