Why is "Memory split" Kconfig option only for EMBEDDED?
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)?
Best,
Norbert
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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
Signature · 2 lines
if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
Quoted 11 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesbecause 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?
</nk>
Quoted 9 lines · Norbert Kiesel
Quoted 8 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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
Quoted 8 lines
Quoted 3 lines
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?
I said *userspace ABI*. You're changing something that userspace has known about and was documented since the start of Linux. So userspace application binaries can break, and at least you're changing the rules on them. That's fine if you know what you're doing.. but in a general system... not a good default, hence the EMBEDDED.
I assumed entirely that you're not using binary drivers, those are just horrid in the first place :)
Signature · 2 lines
if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
Quoted 19 lines · Arjan van de Ven
Quoted 9 lines · Norbert Kiesel
Quoted 8 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesQuoted 8 lines
Quoted 3 lines
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?
Quoted 5 lines
I said *userspace ABI*. You're changing something that userspace has known about and was documented since the start of Linux. So userspace application binaries can break, and at least you're changing the rules on them. That's fine if you know what you're doing.. but in a general system... not a good default, hence the EMBEDDED.
Thanks for the reply. I was not asking to change the default, I just want to see the option in e.g. menuconfig. And the help text already has a very strong advise to leave it at VMSPLIT_3G.
Anyway, I don't want to stress this further: I'm happy enough with my Kconfig that has "if EMBEDDED" removed for the prompt.
Best,
Norbert
Quoted 28 lines · Norbert Kiesel
Quoted 20 lines · Arjan van de Ven
Quoted 10 lines · Norbert Kiesel
Quoted 9 lines · Arjan van de Ven
Quoted 7 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesQuoted 8 lines
Quoted 3 lines
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?Quoted 6 lines
I said *userspace ABI*. You're changing something that userspace has known about and was documented since the start of Linux. So userspace application binaries can break, and at least you're changing the rules on them. That's fine if you know what you're doing.. but in a general system... not a good default, hence the EMBEDDED.
Quoted 4 lines
Thanks for the reply. I was not asking to change the default, I just want to see the option in e.g. menuconfig. And the help text already has a very strong advise to leave it at
VMSPLIT_3G.
I have not had yet any problems with VMSPLIT_3G_OPT ever since I used it -- which dates back to when it was a feature of Con Kolivas's patchset (known as LOWMEM1G), [even] before it got merged in mainline.
It only seem to break the VMware compilation process, but what they do in the makefiles is not really standard anyhow.
Quoted 2 lines
Anyway, I don't want to stress this further: I'm happy enough with my
Kconfigthat has "if EMBEDDED" removed for the prompt.
-`J'
Quoted 5 lines · Jan Engelhardt
I have not had yet any problems with
VMSPLIT_3G_OPTever since I used it -- which dates back to when it was a feature of Con Kolivas's patchset (known as LOWMEM1G), [even] before it got merged in mainline.
(Excluding the cases Adrian Bunk listed: WINE, which I don't use, and also 'some Java programs' which I have not seen.)
-`J'
Quoted 9 lines · Norbert Kiesel
Quoted 8 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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
Quoted 8 lines
Quoted 3 lines
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.
Quoted 1 line
</nk>
cu
Adrian
Signature · 4 lines
"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 SeedQuoted 14 lines · El Wed, 6 Dec 2006 14:10:03 +0100 Adrian Bunk <[email protected]> escribió:
Quoted 13 lines · Norbert Kiesel
Quoted 11 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesbecause it changes the userspace ABI and has some other caveats.... this is not something you should muck with lightly
Quoted 7 lines
Quoted 4 lines
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, butVMSPLIT_2Gdefinitely breaks Wine)
I use VMSPLIT_3G_OPT=y and wine works just fine (only tested with one program). Edgy + 2.6.19-rc1
Quoted 11 lines
- 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.
Quoted 1 line
</nk>
cu
Adrian
Quoted 22 lines · Alejandro Riveira Fernández
Quoted 19 lines · El Wed, 6 Dec 2006 14:10:03 +0100 Adrian Bunk <[email protected]> escribió:
Quoted 17 lines · Norbert Kiesel
Quoted 11 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesbecause 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?
Quoted 14 lines
Quoted 2 lines
- Wine doesn't work (I'm not sure about
VMSPLIT_3G_OPT, butVMSPLIT_2Gdefinitely breaks Wine)I use VMSPLIT_3G_OPT=y and wine works just fine (only tested with one program). Edgy + 2.6.19-rc1
Quoted 6 lines
- 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.
--- arch/i386/Kconfig | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
arch/i386/Kconfig +5 -5
@@ -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
Quoted 34 lines · Norbert Kiesel
Quoted 33 lines · Alejandro Riveira Fernández
Quoted 14 lines · El Wed, 6 Dec 2006 14:10:03 +0100 Adrian Bunk <[email protected]> escribió:
Quoted 13 lines · Norbert Kiesel
Quoted 11 lines · Arjan van de Ven
Quoted 6 lines · Norbert Kiesel
Hi,
I remember reading on LKML some time ago that using
VMSPLIT_3G_OPTwould 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 machinesbecause it changes the userspace ABI and has some other caveats.... this is not something you should muck with lightly
Quoted 7 lines
Quoted 4 lines
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, butVMSPLIT_2Gdefinitely breaks Wine)I use VMSPLIT_3G_OPT=y and wine works just fine (only tested with one program). Edgy + 2.6.19-rc1
Quoted 3 lines
- AFAIR some people reported problems with some Java programs after fiddling with the vmsplit options
Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
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),
...
As I said, VMSPLIT_2G does break Wine for me.
cu
Adrian
Signature · 4 lines
"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 SeedHi!
Quoted 5 lines
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
There's a big difference between 'experimental' and 'known to broke obscure userspace apps'.
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 10 lines · Pavel Machek
Hi!
Quoted 5 lines
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
There's a big difference between 'experimental' and 'known to broke obscure userspace apps'.
True, but abusing EMBEDDED for "only do that if you know what you are doing and if it breaks, you have to keep the pieces" is not good either.
Some other places that seem to fall into the same category are IPX_INTERN ("...This might break existing applications...") which is neither EMBEDDED nor EXPERIMENTAL or RMW_INSNS ("...It is very likely that this will cause serious problems on any Amiga...") that is dependent on ADVANCED.
Anyway, perhaps I should just select EMBEDDED although I don't have a small system (though a 6 year old 1Ghz K7 with 1GB mem might be considered small by some people these days :-), and ignore all the other options that pop up through this.
Best,
Norbert