From: Mark de Vries <m.devries@nl.tiscali.com>
To: linux-kernel@vger.kernel.org
Subject: Re: About highmem in 2.6
Date: Wed, 11 Feb 2004 20:13:10 +0100 [thread overview]
Message-ID: <402A7EC6.7010003@nl.tiscali.com> (raw)
In-Reply-To: <1o7AZ-3PD-9@gated-at.bofh.it>
Dave McCracken wrote:
> --On Wednesday, February 11, 2004 18:47:04 +0100 Luis Miguel García
> <ktech@wanadoo.es> wrote:
>
>
>>When I first installed 2.4, someone told me that if I had 1 gb ram it was
>>better to not use highmem because those extra aditional mb was not worth
>>the speed penalty of using the feature.
>>
>>Sorry for my ignorance (and my sucking english) but must I enable highmem
>>now with 2.6? or have it any speed penalty althought?
>
>
> I don't know if anyone has actually measured the relative performance, but
> I'd expect the answer to be the same as 2.4. There is a small but
> measurable performance penalty for enabling highmem which is higher than
> the benefit of the extra 128 meg of memory you get when you have 1G. If
> you have more than 1G it's better to enable highmem.
>
I've been using this patch for a while now on my box (with 1GB):
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23aa1/00_3.5G-address-space-5
(kernel is 'vanilla' otherwise)
This allows you to use your full 1GB w/out highmem support.... (2G/2G
user/kernel addr space split, or something..)
Anything (potentially) wrong/bad about this patch??
Is there a simmilar patch for 2.6??
Rgds,
Mark.
pls. CC in reply, I'm not on the list....
next parent reply other threads:[~2004-02-11 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1o6EZ-2zO-27@gated-at.bofh.it>
[not found] ` <1o7AZ-3PD-9@gated-at.bofh.it>
2004-02-11 19:13 ` Mark de Vries [this message]
2004-02-11 19:28 ` About highmem in 2.6 Bongani Hlope
2004-02-12 4:02 ` Krzysztof Halasa
2004-02-12 16:07 ` Brandon Low
[not found] ` <Pine.LNX.4.58.0402120945340.1009@fgevxr.nfculk.yna>
2004-02-14 1:54 ` Krzysztof Halasa
2004-02-12 6:48 ` Martin J. Bligh
2004-02-11 17:47 Luis Miguel García
2004-02-11 18:44 ` Dave McCracken
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=402A7EC6.7010003@nl.tiscali.com \
--to=m.devries@nl.tiscali.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.