LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Norbert Kiesel <nkiesel@tbdnetworks.com>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
Date: Sat, 09 Dec 2006 16:45:04 +0100	[thread overview]
Message-ID: <1165679105.7455.116.camel@titan.tbdnetworks.com> (raw)
In-Reply-To: <20061209132742.7a25dcb5@localhost.localdomain>

On Sat, 2006-12-09 at 13:27 +0100, Alejandro Riveira Fernández wrote:
> El Wed, 6 Dec 2006 14:10:03 +0100
> Adrian Bunk <bunk@stusta.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.
> > 

So far all first-hand experiences I heard of were positive (i.e. I did
not get an emaail from anyone saying: It had a negative effect for me),
so I propose to apply the patch from Con Kolivas. The wording in the
description still very strongly recommends to not change that value, and
it's still dependent on EXPERIMENTAL. I append the patch just because
it's short, it's also available from
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.19/2.6.19-ck2/patches/kconfig-expose_vmsplit_option.patch

The options to alter the vmsplit to enable more lowmem are hidden behind the
embedded option. Make it more exposed for -ck users and make the help menu
more explicit about what each option means.

Signed-off-by: Con Kolivas <kernel@kolivas.org>

---
 arch/i386/Kconfig |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

Index: linux-2.6.19-ck2/arch/i386/Kconfig
===================================================================
--- linux-2.6.19-ck2.orig/arch/i386/Kconfig	2006-11-30 11:30:32.000000000 +1100
+++ linux-2.6.19-ck2/arch/i386/Kconfig	2006-12-09 09:01:36.000000000 +1100
@@ -500,7 +500,7 @@ endchoice
 
 choice
 	depends on EXPERIMENTAL
-	prompt "Memory split" if EMBEDDED
+	prompt "Memory split"
 	default VMSPLIT_3G
 	help
 	  Select the desired split between kernel and user memory.
@@ -519,14 +519,14 @@ choice
 	  option alone!
 
 	config VMSPLIT_3G
-		bool "3G/1G user/kernel split"
+		bool "Default 896MB lowmem (3G/1G user/kernel split)"
 	config VMSPLIT_3G_OPT
 		depends on !HIGHMEM
-		bool "3G/1G user/kernel split (for full 1G low memory)"
+		bool "1GB lowmem (3G/1G user/kernel split)"
 	config VMSPLIT_2G
-		bool "2G/2G user/kernel split"
+		bool "2GB lowmem (2G/2G user/kernel split)"
 	config VMSPLIT_1G
-		bool "1G/3G user/kernel split"
+		bool "3GB lowmem (1G/3G user/kernel split)"
 endchoice
 
 config PAGE_OFFSET



  reply	other threads:[~2006-12-09 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 11:42 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
2006-12-09 12:27       ` Alejandro Riveira Fernández
2006-12-09 15:45         ` Norbert Kiesel [this message]
2006-12-09 16:01           ` Adrian Bunk
2006-12-14 14:47           ` Pavel Machek
2006-12-14 15:24             ` Norbert Kiesel
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=1165679105.7455.116.camel@titan.tbdnetworks.com \
    --to=nkiesel@tbdnetworks.com \
    --cc=ariveira@gmail.com \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Why is "Memory split" Kconfig option only for EMBEDDED?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).