linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Christoph Hellwig <hch@infradead.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.73-mm2
Date: Sat, 28 Jun 2003 17:34:05 -0700	[thread overview]
Message-ID: <56960000.1056846845@[10.10.2.4]> (raw)
In-Reply-To: <20030628170837.A10514@infradead.org>

--Christoph Hellwig <hch@infradead.org> wrote (on Saturday, June 28, 2003 17:08:37 +0100):

> On Sat, Jun 28, 2003 at 08:54:36AM -0700, William Lee Irwin III wrote:
>> +config HIGHPMD
>> +	bool "Allocate 2nd-level pagetables from highmem"
>> +	depends on HIGHMEM64G
>> +	help
>> +	  The VM uses one pmd entry for each pagetable page of physical
>> +	  memory allocated. For systems with extreme amounts of highmem,
>> +	  this cannot be tolerated. Setting this option will put
>> +	  userspace 2nd-level pagetables in highmem.
> 
> Does this make sense for !HIGHPTE?  In fact does it make sense to
> carry along HIGHPTE as an option still? ..

Last time I measured it, it had about a 10% overhead in kernel time.
Seems like a good thing to keep as an option to me. Bill said he
had some other code to alleviate the overhead, but I don't think
it's merged ... I'd rather see UKVA (permanently map the pagetables
on a per-process basis) merged before it becomes "not an option" -
that gets rid of all the kmapping.
 
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-06-29  0:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28  3:21 2.5.73-mm2 Andrew Morton
2003-06-28  8:56 ` 2.5.73-mm2 William Lee Irwin III
2003-06-28 15:54 ` 2.5.73-mm2 William Lee Irwin III
2003-06-28 16:08   ` 2.5.73-mm2 Christoph Hellwig
2003-06-28 20:49     ` 2.5.73-mm2 William Lee Irwin III
2003-06-29  0:34     ` Martin J. Bligh [this message]
2003-06-29  2:18       ` 2.5.73-mm2 William Lee Irwin III
2003-06-29  3:07         ` 2.5.73-mm2 Martin J. Bligh
2003-06-28 23:00   ` 2.5.73-mm2 Andrew Morton
2003-06-28 23:11     ` 2.5.73-mm2 William Lee Irwin III
2003-06-29 12:45       ` 2.5.73-mm2 Zwane Mwaikambo
2003-07-02  3:11   ` 2.5.73-mm2 William Lee Irwin III
2003-07-01  0:39 ` 2.5.73-mm2 William Lee Irwin III
2003-07-01  2:14   ` 2.5.73-mm2 Andrew Morton
2003-07-01  2:46     ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 10:46   ` 2.5.73-mm2 Hugh Dickins
2003-07-01 10:51     ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 11:08       ` 2.5.73-mm2 Hugh Dickins
2003-07-01 11:08         ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 12:39           ` 2.5.73-mm2 Nikita Danilov
2003-07-01  5:56 ` 2.5.73-mm2 William Lee Irwin III

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='56960000.1056846845@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@digeo.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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