From: Ralf Baechle <ralf@linux-mips.org>
To: Srinivas Kommu <kommu@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: highmem questions
Date: Fri, 4 Aug 2006 00:51:51 +0100 [thread overview]
Message-ID: <20060803235151.GA30970@linux-mips.org> (raw)
In-Reply-To: <44D12317.7090002@hotmail.com>
On Wed, Aug 02, 2006 at 03:11:35PM -0700, Srinivas Kommu wrote:
> 1. If I have 1 gig physical memory and CONFIG_HIGHMEM disabled, would
> the user processes be able to see the high memory?
> Only 256 meg (this is on BCM1250; so 256 meg is expected) shows up in
> /proc/meminfo and I couldn't malloc more than that much from user processes.
While I've originally implemented highmem for the BCM1250 in early 2002
highmem is and stays the same stupid idea it was back then. Go for a
64-bit kernel, it's far less headache. If you don't want to run 64-bit
binaries applications, run a standard 32-bit distribution.
> 2. With highmem enabled, is there a penalty to the user processes? From
> what I understood, highmem mappings are needed for the kernel to access
> that memory. For the pages belonging to user processes, does it still
> use pkmaps?
User process performance is identical. The performance penalty is on I/O
or any sort of kernel activity on highmem pages..
> 3. How do I measure the penalty of highmem on kernel modules? Since the
> code and data for modules resides in highmem, the kernel has to
> constantly map and unmap while running inside the modules? Is there a
> way to quantify the overhead of running with highmem enabled versus not?
The physical address of modules does not make any difference.
Highmem, just say no.
Ralf
prev parent reply other threads:[~2006-08-04 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 22:11 highmem questions Srinivas Kommu
2006-08-03 23:51 ` Ralf Baechle [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=20060803235151.GA30970@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kommu@hotmail.com \
--cc=linux-mips@linux-mips.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