From: Ryan Cumming <ryan@spitfire.gotdns.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-ck1
Date: Sun, 15 Aug 2004 10:11:18 -0700 [thread overview]
Message-ID: <200408151011.20327.ryan@spitfire.gotdns.org> (raw)
In-Reply-To: <411F6679.5080008@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Sunday 15 August 2004 06:34, Con Kolivas wrote:
> +1g_lowmem_i386.diff
> Allows 1Gb of ram to be used without enabling highmem
Note that valgrind 2.x (a fairly powerful memory debugger/profiler) hates
this. It dies with:
executable is mapped outside of range 0x80d7000-0xaffff000
failed to load /usr/lib/valgrind/stage2: Cannot allocate memory
Haven't looked in to how easy this is to hack around, just a heads up.
-Ryan
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-15 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 13:34 2.6.8.1-ck1 Con Kolivas
2004-08-15 17:11 ` Ryan Cumming [this message]
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=200408151011.20327.ryan@spitfire.gotdns.org \
--to=ryan@spitfire.gotdns.org \
--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