From: David Klempner <klempner@imsanet.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2GB of RAM
Date: Wed, 21 Jun 2006 11:04:46 -0500 [thread overview]
Message-ID: <20060621160446.GA27868@kenmore.strcpy.org> (raw)
In-Reply-To: <44990B77.8050800@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
* Ralph Slooten <axllent@gmail.com> [2006-06-21 04:12]:
> Sorry, but one thing remains unclear. Ignoring the fact that adding
> embedded extras to your kernel on a non-embedded system just to get the
> the VMSPLIT options is (in my opinion) confusing and unlogical, is this
> step actually needed considering I (according to your advice) would take
> the default VMSPLIT anyway?
> What I mean is simply: If I enable HIGHMEM4GB to allow the kernel to use
> my 2GB of RAM, do I still need to add the embedded options (as you
> explain above), or is simply using HIGHMEM4GB enough? It's maybe a tough
> question is ask, but you definitely seem to know exactly what you are
> talking about ;-)
Right; the right thing to do here is to not touch VMSPLIT at all, which
means there's no reason to be messing around with CONFIG_EMBEDDED. Just
set HIGHMEM4GB and be done with it (but, if you're editing a config
where you've already done so, make sure that you still have all of the
CONFIG_EMBEDDED dependent options set correctly before you unset it:
enable every one of the "standard kernel features" except for the extra
pass, and then make sure you have the default 3/1 VMSPLIT)
> > Hope this helps.
>
> Is sure does! Any advice to the above question? With that I should be
> complete I think ;-) Where do you get your information from btw (I'm
> curious as I didn't find much via Google explaining as clear as you did)?
I did some googling about a year and a half ago, when I finally upgraded
my desktop from 512MB to 1GB and ran into these issues for the first
time, and I've spent some time poking around the kernel sources before.
--
David Klempner
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-21 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 17:45 [gentoo-user] 2GB of RAM Ralph Slooten
2006-06-18 18:44 ` Steven Susbauer
2006-06-19 5:00 ` Ralph Slooten
2006-06-18 19:17 ` David Klempner
2006-06-19 5:17 ` Ralph Slooten
2006-06-19 6:17 ` David Klempner
2006-06-19 7:19 ` Ralph Slooten
2006-06-20 16:01 ` Vladimir G. Ivanovic
2006-06-20 16:14 ` Justin R Findlay
2006-06-20 16:45 ` Mike Huber
2006-06-20 16:16 ` Justin Piszcz
2006-06-20 17:43 ` Graham Murray
2006-06-20 19:05 ` David Klempner
2006-06-20 19:36 ` Vladimir G. Ivanovic
2006-06-20 20:01 ` David Klempner
2006-06-20 21:40 ` Vladimir G. Ivanovic
2006-06-21 6:21 ` David Klempner
2006-06-21 16:03 ` Vladimir G. Ivanovic
2006-06-20 20:08 ` David Klempner
2006-06-21 5:08 ` Ralph Slooten
2006-06-21 6:16 ` David Klempner
2006-06-21 9:03 ` Ralph Slooten
2006-06-21 16:04 ` David Klempner [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=20060621160446.GA27868@kenmore.strcpy.org \
--to=klempner@imsanet.org \
--cc=gentoo-user@lists.gentoo.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