From: Michael Bacarella <mbac@nyct.net>
To: jlnance@intrex.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is the truth about Linux 2.4's RAM limitations?
Date: Mon, 9 Jul 2001 23:29:03 -0400 [thread overview]
Message-ID: <20010709232903.A29136@sync.nyct.net> (raw)
In-Reply-To: <Pine.LNX.4.32.0107091250170.25061-100000@maus.spack.org> <20010709230151.A13704@bessie.localdomain>
In-Reply-To: <20010709230151.A13704@bessie.localdomain>; from jlnance@intrex.net on Mon, Jul 09, 2001 at 11:01:51PM -0400
On Mon, Jul 09, 2001 at 11:01:51PM -0400, jlnance@intrex.net wrote:
> Next I patched the hoard allocator so that instead of calling mmap(0, ...)
> it would call it as something like mmap(0x10000000, ...) which causes it
> to start allocating memory that would normally be reserved for sbrk().
> I think I could get close to 2.5G from the hoard malloc after this patch.
> This change got incorporated into the latest hoard, but I had problems
> building the latest hoard, so you may want to wait for a future release.
>
> Anyway, I just wanted to let you know that there are some glibc issues that
> are more restrictive than the kernel issues.
dietlibc is pretty funky:
http://www.fefe.de/dietlibc/
I'm not sure if it's memory usage patterns are all that different from
glibc (as I haven't checked). If so, it may still be easier to
hack than something as uh.. established.. as glibc.
--
Michael Bacarella <mbac@nyct.net>
Technical Staff / System Development,
New York Connect.Net, Ltd.
next prev parent reply other threads:[~2001-07-10 3:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 20:01 What is the truth about Linux 2.4's RAM limitations? Adam Shand
2001-07-09 21:15 ` Brian Gerst
2001-07-09 21:18 ` Rik van Riel
2001-07-09 22:17 ` Matti Aarnio
2001-07-10 13:49 ` Chris Wedgwood
2001-07-10 17:03 ` Timur Tabi
2001-07-10 17:35 ` Richard B. Johnson
2001-07-10 18:01 ` Timur Tabi
2001-07-10 18:08 ` Jonathan Lundell
2001-07-10 18:45 ` Richard B. Johnson
2001-07-10 19:26 ` Jonathan Lundell
2001-07-10 23:56 ` Jesse Pollard
2001-07-10 20:19 ` Malcolm Beattie
2001-07-10 3:01 ` jlnance
2001-07-10 3:29 ` Michael Bacarella [this message]
2001-07-16 8:37 ` Ingo Oeser
[not found] <Pine.LNX.4.32.0107091250170.25061-100000@maus.spack.org.suse.lists.linux.kernel>
2001-07-09 21:03 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-07-09 21:29 Jesse Pollard
2001-07-10 17:01 ` Timur Tabi
2001-07-10 18:12 Jesse Pollard
2001-07-10 18:22 ` Jonathan Lundell
2001-07-10 18:28 ` Brian Gerst
2001-07-10 18:43 ` Chris Wedgwood
2001-07-10 19:35 ` Brian Gerst
2001-07-10 18:38 Jesse Pollard
2001-07-10 19:14 ` Mark H. Wood
2001-07-10 21:49 Jesse Pollard
2001-07-10 22:07 ` Jonathan Lundell
2001-07-11 4:31 alad
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=20010709232903.A29136@sync.nyct.net \
--to=mbac@nyct.net \
--cc=jlnance@intrex.net \
--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