From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'David Gibson'" <david@gibson.dropbear.id.au>
Cc: <linux-kernel@vger.kernel.org>, <linux-ia64@vger.kernel.org>,
<lse-tech@lists.sourceforge.net>, <raybry@sgi.com>,
"'Andy Whitcroft'" <apw@shadowen.org>,
"Andrew Morton" <akpm@osdl.org>
Subject: RE: hugetlb demand paging patch part [0/3]
Date: Thu, 15 Apr 2004 20:43:08 -0700 [thread overview]
Message-ID: <200404160343.i3G3h8F13447@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040416033251.GH12735@zax>
David Gibson wrote on Thursday, April 15, 2004 8:33 PM
> To unify even the non-ppc64 archs we already have to allow for the
> hugepage pagetables to have different structure across archs - on i386
> and ppc64 the hugePTEs lie in PMD slots, on sparc64 and sh they lie in
> (normal) PTE slots and on IA64 they lie in the PTE slots of a special
> set of pagetables. Given that, it seems conceptually logical to me
> that we also not assume the hugepage PTEs have the same layout as
> normal PTEs. It makes the handle_mm_fault function not the least more
> complicated.
Correction: huge page pte on ia64 has the same format as a normal page pte.
next prev parent reply other threads:[~2004-04-16 3:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 23:17 Chen, Kenneth W
2004-04-14 9:04 ` Arjan van de Ven
2004-04-14 10:08 ` Andy Whitcroft
2004-04-14 15:21 ` [Lse-tech] " Martin J. Bligh
2004-04-14 15:23 ` Martin J. Bligh
2004-04-15 1:23 ` David Gibson
2004-04-15 6:42 ` David Gibson
2004-04-15 17:08 ` Chen, Kenneth W
2004-04-16 1:30 ` 'David Gibson'
2004-04-16 3:01 ` Chen, Kenneth W
2004-04-16 3:32 ` 'David Gibson'
2004-04-16 3:43 ` Chen, Kenneth W [this message]
2004-04-16 4:02 ` 'David Gibson'
[not found] <7A4826DE8867D411BAB8009027AE9EB91DB42C83@scsmsx401.sc.intel.com>
2004-04-15 18:42 ` Chen, Kenneth W
2004-04-16 1:38 ` 'David Gibson'
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=200404160343.i3G3h8F13447@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=raybry@sgi.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
all inboxes | Powered by JetHome®