From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: brian@worldcontrol.com
Cc: "Gabriel.Leen" <Gabriel.Leen@ul.ie>,
"'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Re: Process not given >890MB on a 4MB machine ?????????
Date: 20 Sep 2001 22:36:06 +0200 [thread overview]
Message-ID: <m23d5heh1l.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <20010920125616.A14985@top.worldcontrol.com> (brian@worldcontrol.com's message of "Thu, 20 Sep 2001 12:56:16 -0700")
brian@worldcontrol.com writes:
> > The problem in a nutshell is:
> >
> > a) I have a 4GB ram 1.7Gh Xeon box
> > b) I'm running a process which requires around 3GB of ram
> > c) RedHat 2.4.9 will only give it 890MB, then core dumps with the warning
> > "segmentation fault"
> > when it reaches this memory usage and "asks for more"
>
> That is exacly what I've seen.
>
> The limit I ran into was in glibc. My code used malloc, and apparently
> some versions of malloc in glibc try "harder" than others to allocate
> memory. Check your version of glibc and try a later one if available.
the problem is that the glibc has various algo to allocate memory, depending of
the requested size (greater than a page or not), and use the "classic" sbrk() if
lesser (bellow 1Gb) or an anonymous mapping (from 1Gb to a limit that depends of
the virtual memory split between the kernel and the process space).
therefore small malloc will eat space below 1GB and cannot use more than this GB
(minus the process text & data).
anyway for small objects set, there's more efficient techniques (one big malloc
is less costly than several small malloc()).
--
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-mm.org/
next prev parent reply other threads:[~2001-09-20 20:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 19:25 Gabriel.Leen
2001-09-20 19:56 ` brian
2001-09-20 20:36 ` Thierry Vignaud [this message]
2001-09-20 20:56 ` Benjamin LaHaise
2001-09-21 8:29 ` Eric W. Biederman
2001-09-21 16:07 Gabriel.Leen
2001-09-22 2:01 ` Rik van Riel
2001-09-24 21:15 Gabriel.Leen
2001-09-24 22:16 ` Jonathan Morton
2001-09-24 22:41 Gabriel.Leen
2001-09-24 21:16 ` Joseph A Knapka
2001-09-25 10:59 ` Stephen C. Tweedie
2001-09-25 17:36 ` afei
2001-09-26 7:04 ` Eric W. Biederman
2001-09-26 8:53 ` Stephen C. Tweedie
[not found] <5D2F375D116BD111844C00609763076E050D1681@exch-staff1.ul.ie>
2001-09-24 22:49 ` Rik van Riel
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=m23d5heh1l.fsf@vador.mandrakesoft.com \
--to=tvignaud@mandrakesoft.com \
--cc=Gabriel.Leen@ul.ie \
--cc=brian@worldcontrol.com \
--cc=linux-mm@kvack.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