From: Andrew Morton <akpm@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ak@suse.de, david@gibson.dropbear.id.au,
linux-kernel@vger.kernel.org, anton@samba.org, paulus@samba.org,
linuxppc64-dev@lists.linuxppc.org
Subject: Re: RFC: COW for hugepages
Date: Wed, 7 Apr 2004 19:01:26 -0700 [thread overview]
Message-ID: <20040407190126.06a9c38f.akpm@osdl.org> (raw)
In-Reply-To: <1081386710.1401.86.camel@gaston>
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
>
> > Implementing this for ppc64 only is just wrong. Before you do this
> > I would suggest to factor out the common code in the various hugetlbpage
> > implementations and then implement it in common code.
>
> Have you actually looked at it and how huge pages are implemented
> on the various architectures ?
>
> Honestly, I don't think we have any common abstraction on things
> like hugepte's etc... actually, archs aren't even required to use
> PTEs at all.
>
> I don't see how we can make that code arch-neutral, at least not
> without a major redesign of the whole large pages mecanism.
I don't see much in the COW code which is ppc64-specific. All the hardware
needs to do is to provide a way to make the big pages readonly. With a bit
of an abstraction for the TLB manipulation in there it should be pretty
straightforward.
Certainly worth the attempt, no?
next prev parent reply other threads:[~2004-04-08 2:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 7:42 RFC: COW for hugepages David Gibson
2004-04-07 7:53 ` Andrew Morton
2004-04-07 8:03 ` Anton Blanchard
2004-04-07 8:29 ` Benjamin Herrenschmidt
2004-04-08 1:57 ` David Gibson
2004-04-07 9:00 ` Zoltan Menyhart
2004-04-08 1:53 ` David Gibson
2004-04-08 11:10 ` Zoltan Menyhart
2004-04-08 14:19 ` David Gibson
2004-04-07 12:34 ` Andi Kleen
2004-04-07 14:27 ` Anton Blanchard
2004-04-07 14:50 ` Andi Kleen
2004-04-07 21:41 ` Anton Blanchard
2004-04-07 21:47 ` Andi Kleen
2004-04-08 1:11 ` Benjamin Herrenschmidt
2004-04-08 2:01 ` Andrew Morton [this message]
2004-04-08 3:09 ` David Gibson
2004-04-08 3:24 ` Andrew Morton
2004-04-08 3:56 ` David Gibson
2004-04-08 1:50 ` David Gibson
2004-04-07 15:21 ` Dave Hansen
2004-04-08 3:22 ` 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=20040407190126.06a9c38f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).