linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: benh@kernel.crashing.org, ak@suse.de,
	linux-kernel@vger.kernel.org, anton@samba.org, paulus@samba.org,
	linuxppc64-dev@lists.linuxppc.org
Subject: Re: RFC: COW for hugepages
Date: Thu, 8 Apr 2004 13:56:45 +1000	[thread overview]
Message-ID: <20040408035645.GC29551@zax> (raw)
In-Reply-To: <20040407202443.78078b59.akpm@osdl.org>

On Wed, Apr 07, 2004 at 08:24:43PM -0700, Andrew Morton wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > > 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?
> > 
> >  Yes, you have a point.  However doing it in a cross-arch way will
> >  require building more of a shared abstraction about hugepage pte
> >  entries that exists currently.  And that will mean making significant
> >  changes to all the archs to create that abstraction.  I don't know
> >  enough about the other archs to be confident of debugging such
> >  changes, but I'll see what I can do.
> 
> Well the first step is to consolidate the existing duplication in 2.6.5
> before thinking about new features.  That's largely a cut-n-paste job which
> I've been meaning to get onto but alas have not.  I don't want to dump it
> on you just because you want to tend to your COWs so if you have other
> things to do, please let me know.

Well, I do have other things to do, so I'll try to look at the
consolidation when I get a chance.

> We could use the `weak' attribute in mm/hugetlbpage.c for those cases where
> one arch really needs to do something different.

Yes, that's an idea.

-- 
David Gibson			| For every complex problem there is a
david AT gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

  reply	other threads:[~2004-04-08  4:19 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
2004-04-08  3:09       ` David Gibson
2004-04-08  3:24         ` Andrew Morton
2004-04-08  3:56           ` David Gibson [this message]
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=20040408035645.GC29551@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --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).