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 17:08:22 +0000 [thread overview]
Message-ID: <200404151708.i3FH8MF08394@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040415064259.GD25560@zax>
In-Reply-To: <200404132317.i3DNH4F21162@unix-os.sc.intel.com>
>>>> David Gibson wrote on Wednesday, April 14, 2004 11:43 PM
> >
> > Some caveats: I don't have sh and sparc64 hardware to test. But hugetlb
> > code in these two arch looked like a triplet twin of x86 code. So I'm
> > pretty sure it will work right out of box. I've monkeyed around with
> > ppc64 code and after a while I realized it should be left for the experts.
> > I'm sure there are plenty ppc64 developers out there that can get it done
> > in no time.
>
> To the extent that I understand your patches, it shouldn't be that
> hard to adapt for ppc64, with one caveat: on ppc64, unlike the other
> hugepage archs, the format of hugepage PTEs is not identical to the
> format of normal PTEs. So to do this for ppc64, the generic parts of
> your code will need to use a hugepte_t instead of pte_t - it can be
> typedeffed to pte_t on archs other than ppc64. Likewise there will
> need to be hugepte_none() and so forth macros.
I think it would be cleaner if ppc64 change its format instead of changing
4 other arch to accommodate ppc64. By the way, why do you need to special
typedef hugepte_t? pte for huge page aren't anything special on all other
arches.
- Ken
next prev parent reply other threads:[~2004-04-15 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7A4826DE8867D411BAB8009027AE9EB91DB42C83@scsmsx401.sc.intel.com>
2004-04-13 23:17 ` hugetlb demand paging patch part [0/3] 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 [this message]
2004-04-16 1:30 ` 'David Gibson'
2004-04-15 18:42 ` Chen, Kenneth W
2004-04-16 1:38 ` '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
2004-04-16 4:02 ` '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=200404151708.i3FH8MF08394@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