From: Andrew Clayton <andrew@digital-domain.net>
To: Chase Venters <chase.venters@clientec.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: VMSPLIT kernel config option
Date: Mon, 12 Jun 2006 22:07:27 +0100 [thread overview]
Message-ID: <20060612220727.4bd12759@alpha.digital-domain.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0606121552380.17886@turbotaz.ourhouse>
On Mon, 12 Jun 2006 15:55:23 -0500 (CDT), Chase Venters wrote:
> On Mon, 12 Jun 2006, Andrew Clayton wrote:
>
> > Hi,
> >
> > Is it meant, that the VMSPLIT_* options are only enabled
> > "if EMBEDDED"?
>
> Indeed. Unfortunately, adjusting VMSPLIT appeared to break the
> assumptions of some programs like Valgrind (and hence caused a
> regression for some users). VMSPLIT was thusly "hidden" under
> CONFIG_EMBEDDED such that the only people who would be inclined to
> mess with the setting were people already tinkering with "low-level"
> settings if you will.
Ah, understood.
Cheers,
Andrew
next prev parent reply other threads:[~2006-06-12 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 20:54 VMSPLIT kernel config option Andrew Clayton
2006-06-12 20:55 ` Chase Venters
2006-06-12 21:07 ` Andrew Clayton [this message]
2006-06-12 20:57 ` Mark Lord
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=20060612220727.4bd12759@alpha.digital-domain.net \
--to=andrew@digital-domain.net \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
/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