From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Raymond Nijssen <raymond@zeropage.com>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: maximum memory limit
Date: Mon, 3 Jul 2000 17:01:36 +0200 [thread overview]
Message-ID: <20000703170136.A30511@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20000703151823.D3284@redhat.com>; from sct@redhat.com on Mon, Jul 03, 2000 at 03:18:23PM +0100
Stephen C. Tweedie wrote:
> > There are lots of custom malloc libraries. If you're going to teach
> > Glibc something anyway, why not add a new mmap flag?
>
> Because by the time glibc has been loaded, it's too late! We need the
> crt0.o stub to load libdl.so lower in memory or we have already
> clobbered the address space irretrievably.
?? /lib/ld-linux.so.2 is loaded by the kernel so you can easily changed
the way it is mapped. Everything from there on is part of Glibc.
The only exception is statically linked binaries, and they're not going
to switch to a new malloc anyway.
-- Jamie
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-07-03 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <381740616.949993193648.JavaMail.root@web36.pub01>
2000-02-08 14:08 ` Rik van Riel
2000-02-08 14:48 ` Matthew Kirkwood
2000-02-08 15:04 ` Mark Hahn
2000-02-08 15:25 ` Jakub Jelinek
2000-02-08 16:13 ` Rogier Wolff
2000-02-08 16:25 ` Eric W. Biederman
2000-07-02 5:35 ` Raymond Nijssen
2000-07-03 10:35 ` Stephen C. Tweedie
2000-07-03 13:32 ` Jamie Lokier
2000-07-03 14:18 ` Stephen C. Tweedie
2000-07-03 15:01 ` Jamie Lokier [this message]
2000-07-03 19:32 ` Raymond Nijssen
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=20000703170136.A30511@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=raymond@zeropage.com \
--cc=sct@redhat.com \
/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