From: Adrian Bunk <bunk@stusta.de>
To: Norbert Kiesel <nkiesel@tbdnetworks.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
Date: Wed, 6 Dec 2006 14:10:03 +0100 [thread overview]
Message-ID: <20061206131003.GF24140@stusta.de> (raw)
In-Reply-To: <1165407548.5954.224.camel@titan.tbdnetworks.com>
On Wed, Dec 06, 2006 at 01:19:08PM +0100, Norbert Kiesel wrote:
> On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote:
> > On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
> > > Hi,
> > >
> > > I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
> > > be optimal for a machine with exactly 1GB memory (like my current
> > > desktop). Why is that option only prompted for after selecting EMBEDDED
> > > (which I normally don't select for desktop machines
> >
> > because it changes the userspace ABI and has some other caveats.... this
> > is not something you should muck with lightly
> >
>
> Hmm, but it's also marked EXPERIMENTAL. Would that not be the
> sufficient? Assuming I don't use any external/binary drivers and a
> self-compiled kernel w//o any additional patches: is there really any
> downside?
- Wine doesn't work (I'm not sure about VMSPLIT_3G_OPT, but
VMSPLIT_2G definitely breaks Wine)
- AFAIR some people reported problems with some Java programs
after fiddling with the vmsplit options
EMBEDDED isn't exactly the right way to hide it, but the vmsplit options
aren't something you can safely change.
> </nk>
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-12-06 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 11:42 Why is "Memory split" Kconfig option only for EMBEDDED? Norbert Kiesel
2006-12-06 11:58 ` Arjan van de Ven
2006-12-06 12:19 ` Norbert Kiesel
2006-12-06 12:45 ` Arjan van de Ven
2006-12-06 13:36 ` Norbert Kiesel
2006-12-06 21:00 ` Jan Engelhardt
2006-12-06 21:10 ` Jan Engelhardt
2006-12-06 13:10 ` Adrian Bunk [this message]
2006-12-09 12:27 ` Alejandro Riveira Fernández
2006-12-09 15:45 ` Norbert Kiesel
2006-12-09 16:01 ` Adrian Bunk
2006-12-14 14:47 ` Pavel Machek
2006-12-14 15:24 ` Norbert Kiesel
-- strict thread matches above, loose matches on Subject: below --
2006-12-10 4:26 linux
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=20061206131003.GF24140@stusta.de \
--to=bunk@stusta.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nkiesel@tbdnetworks.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