mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrew Morton <akpm@zip.com.au>,
	William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, riel@surriel.com
Subject: Re: fix CONFIG_HIGHPTE
Date: Tue, 06 Aug 2002 22:16:04 -0700	[thread overview]
Message-ID: <1296174189.1028672155@[10.10.2.3]> (raw)
In-Reply-To: <3D506D43.890EA215@zip.com.au>

> And we'll need that, to reduce load on KM_PTECHAIN.  Because
> there's no point in pte_highmem without also having pte_chain_highmem,
> yes?

I'm not sure I agree that there's no point. If we shove half the 
overhead into highmem (well, maybe 1/3 depending if on your PTE size), 
we can fit a workload double the size. Not to be sniffed at. 50% of 
the benefit at 5% of the cost.

No, it doesn't completely solve the problem, but it's another hammer
to give it a good sturdy whack over the head with. 

M.


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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 23:15 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
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 [this message]

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='1296174189.1028672155@[10.10.2.3]' \
    --to=martin.bligh@us.ibm.com \
    --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

all inboxes | Powered by JetHome®