From: Dave McCracken <dmccr@us.ibm.com>
To: Paul P Komkoff Jr <i@stingr.net>,
lkml <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@zip.com.au>
Subject: Re: 2.5.46-mm1
Date: Wed, 06 Nov 2002 13:20:45 -0600 [thread overview]
Message-ID: <192390000.1036610445@baldur.austin.ibm.com> (raw)
In-Reply-To: <20021106171249.GB29935@stingr.net>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
--On Wednesday, November 06, 2002 20:12:50 +0300 Paul P Komkoff Jr
<i@stingr.net> wrote:
> Why sharepte is dependent on highmem now ?
It's not supposed to be. I'm guessing it's a conversion error in the move
to Kconfig. A patch to fix it is attached.
> I thought I will benefit from it on forkloads on lowmem too ...
It's definitely a benefit for all sizes of memory.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
[-- Attachment #2: shpte-2.5.46-mm1-1.diff --]
[-- Type: text/plain, Size: 425 bytes --]
--- 2.5.46-mm1/arch/i386/Kconfig 2002-11-06 13:17:20.000000000 -0600
+++ 2.5.46-mm1-shsent/arch/i386/Kconfig 2002-11-06 11:38:50.000000000 -0600
@@ -722,7 +722,6 @@
config SHAREPTE
bool "Share 3rd-level pagetables between processes"
- depends on HIGHMEM4G || HIGHMEM64G
help
Normally each address space has its own complete page table for all
its mappings. This can mean many mappings of a set of shared data
next prev parent reply other threads:[~2002-11-06 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 8:34 2.5.46-mm1 Andrew Morton
[not found] ` <20021106171249.GB29935@stingr.net>
2002-11-06 19:20 ` Dave McCracken [this message]
2002-11-07 16:41 ` 2.5.46-mm1 Bill Davidsen
2002-11-07 16:51 ` 2.5.46-mm1 Martin J. Bligh
2002-11-07 17:13 ` 2.5.46-mm1 Andrew Morton
2002-11-07 18:45 ` 2.5.46-mm1 Martin J. Bligh
2002-11-07 19:22 ` 2.5.46-mm1 Bill Davidsen
2002-11-07 19:05 ` 2.5.46-mm1 Bill Davidsen
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=192390000.1036610445@baldur.austin.ibm.com \
--to=dmccr@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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