From: Andi Kleen <ak@suse.de>
To: majer@endeca.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: memory allocation problems
Date: Fri, 6 Apr 2001 17:21:55 +0200 [thread overview]
Message-ID: <20010406172155.A17128@gruyere.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0104061001280.9562-300000@caffeine.ops.endeca.com>
In-Reply-To: <Pine.LNX.4.21.0104061001280.9562-300000@caffeine.ops.endeca.com>; from majer@endeca.com on Fri, Apr 06, 2001 at 10:06:47AM -0400
On Fri, Apr 06, 2001 at 10:06:47AM -0400, majer@endeca.com wrote:
> Essentially, the problem can be summarized to be that on a machine
> with ample ram (2G, 4G, etc), I am unable to malloc a gig if I ask
> for the memory in small ( <= 128k) chunks. I've enclosed some results
> and a little program which was put together to demonstrate the problems
> we're having. All of the failures seem to occur around 930MB.
It's bumping against some mapping (just do system("cat /proc/self/maps")
on allocation failure to see which). Usual suspects are shared libraries.
One possible solution is to upgrade to a newer glibc, the 2.2 glibc malloc
should handle this case better.
A way to get mappings like shared libraries out of the way is to
increase the value of TASK_UNMAPPED_BASE in include/asm-i386/processor.h.
For that the kernel needs to be recompiled and it should be smaller
TASK_SIZE-enough space for your shared libraries. With that even the older
malloc will probably work.
-Andi
next prev parent reply other threads:[~2001-04-06 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 14:06 majer
2001-04-06 15:21 ` Andi Kleen [this message]
2001-04-06 16:57 ` Wayne Whitney
2001-04-06 19:22 ` Mark Hahn
2001-04-06 19:40 ` Wayne Whitney
2001-04-06 20:08 ` Mark Hahn
2001-04-06 21:21 ` Hugh Dickins
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=20010406172155.A17128@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=majer@endeca.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
all inboxes | Powered by JetHome®