LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.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 22:00:55 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0612062158010.16042@yvahk01.tjqt.qr> (raw)
In-Reply-To: <1165412195.5954.239.camel@titan.tbdnetworks.com>


On Dec 6 2006 14:36, Norbert Kiesel wrote:
>On Wed, 2006-12-06 at 13:45 +0100, Arjan van de Ven wrote:
>> On Wed, 2006-12-06 at 13:19 +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?
>> 
>> 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.

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.

>Anyway, I don't want to stress this further: I'm happy enough with my
>Kconfig that has "if EMBEDDED" removed for the prompt. 



	-`J'
-- 

  reply	other threads:[~2006-12-06 21:02 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 [this message]
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
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=Pine.LNX.4.61.0612062158010.16042@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkiesel@tbdnetworks.com \
    --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).