public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org, riel@surriel.com
Subject: Re: fix CONFIG_HIGHPTE
Date: Wed, 7 Aug 2002 11:07:52 +1000	[thread overview]
Message-ID: <20020807010752.GC6343@krispykreme> (raw)
In-Reply-To: <3D506D43.890EA215@zip.com.au>

 
> We're piling more and more crap in there to support these pte_chains.
> How much is too much?
> 
> Is it likely that large pages and/or shared pagetables would allow us to
> place pagetables and pte_chains in the direct-mapped region, avoid all
> this?

On ppc64 shared pagetables will require significant changes to the way
we handle the hardware hashtable. So add that to the "more and more crap
in there to support these pte_chains"

Will shared pagetables be a requirement or can we turn it on per arch?

Anton

  parent reply	other threads:[~2002-08-07  1:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 23:15 fix CONFIG_HIGHPTE William Lee Irwin III
2002-08-07  0:43 ` Andrew Morton
2002-08-07  0:50   ` Rik van Riel
2002-08-07  1:31     ` William Lee Irwin III
2002-08-07  4:00       ` Rik van Riel
2002-08-07  4:12         ` William Lee Irwin III
2002-08-07  1:07   ` Anton Blanchard [this message]
2002-08-07  1:55     ` William Lee Irwin III
2002-08-07  2:57     ` Andrew Morton
2002-08-07 18:43       ` Ingo Oeser
2002-08-08 14:51         ` Rik van Riel
2002-08-08 19:59           ` Alan Cox
2002-08-08 18:44             ` Rik van Riel
2002-08-08 19:22             ` William Lee Irwin III
2002-08-08 14:51         ` Martin J. Bligh
2002-08-09 14:10         ` Daniel Phillips
2002-08-09 14:07       ` Daniel Phillips
2002-08-07  4:05     ` Rik van Riel
2002-08-07  4:18       ` Anton Blanchard
2002-08-07  5:16   ` Martin J. Bligh

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=20020807010752.GC6343@krispykreme \
    --to=anton@samba.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.com \
    --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