[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061209132742.7a25dcb5@localhost.localdomain>
Date: Sat, 9 Dec 2006 13:27:42 +0100
From: Alejandro Riveira Fernández
<ariveira@...il.com>
To: Adrian Bunk <bunk@...sta.de>
Cc: Norbert Kiesel <nkiesel@...networks.com>,
Arjan van de Ven <arjan@...radead.org>,
linux-kernel@...r.kernel.org
Subject: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
El Wed, 6 Dec 2006 14:10:03 +0100
Adrian Bunk <bunk@...sta.de> escribió:
> 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)
I use VMSPLIT_3G_OPT=y and wine works just fine (only tested with one
program). Edgy + 2.6.19-rc1
> - 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
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists