From: Dave McCracken <dmccr@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>,
Adam Litke <agl@us.ibm.com>,
wli@holomorphy.com
Subject: Re: [RFC/PATCH] Shared Page Tables [0/2]
Date: Mon, 10 Apr 2006 15:27:48 -0500 [thread overview]
Message-ID: <1083771BBA2E79327C70D039@[10.1.1.4]> (raw)
In-Reply-To: <Pine.LNX.4.64.0604101320100.24029@schroedinger.engr.sgi.com>
--On Monday, April 10, 2006 13:20:59 -0700 Christoph Lameter
<clameter@sgi.com> wrote:
>> The lock changes to hugetlb are only to support sharing of pmd pages when
>> they contain hugetlb pages. They just substitute the struct page lock
>> for the page_table_lock, and are only about 30 lines of code. Is this
>> really worth separating out?
>
> Ia64 does not use pmd pages for huge pages. It relies instead on a
> separate region. I wonder if this works on IA64.
Sharing of hugetlb page tables is enabled on a per-architecture basis, so
if ia64 doesn't use pmd pages we shouldn't try to enable it. If it's not
enabled all the locking in hugetlb resolves to using page_table_lock, so
the original semantics will be preserved.
Dave McCracken
--
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>
prev parent reply other threads:[~2006-04-10 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 16:13 Dave McCracken
2006-04-10 17:22 ` Christoph Lameter
2006-04-10 20:11 ` Dave McCracken
2006-04-10 20:20 ` Christoph Lameter
2006-04-10 20:27 ` Dave McCracken [this message]
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='1083771BBA2E79327C70D039@[10.1.1.4]' \
--to=dmccr@us.ibm.com \
--cc=agl@us.ibm.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
/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