From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: brian@worldcontrol.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Stuck at 1GB again
Date: Sun, 3 Sep 2000 10:26:48 -0700 (PDT) [thread overview]
Message-ID: <200009031726.KAA90541@google.engr.sgi.com> (raw)
In-Reply-To: <20000902115032.A2764@top.worldcontrol.com> from "brian@worldcontrol.com" at Sep 02, 2000 11:50:32 AM
>
> Some time ago, the list was very helpful in solving my programs
> failing at the limit of real memory rather than expanding into
> swap under linux 2.2.
>
I can;t say what your actual problem is, but in previous experiments,
I have seen these as the main cause:
1. shortage of real memory (ram + swap). I don't think this is your
problem.
2. resource limit problems: some resource limits were defined as
"int/long" instead of "unsigned int/long", but these should have
been fixed.
3. inability of malloc to find a contiguous range of virtual space in
userland: this depends on libraries used etc, that eat up chunks of
the user space. This might be your problem. (Hint: code a while(1)
loop before any malloc happens in your program, then use "cat
/proc/pid/maps", where pid is the pid of your running program, to
see the user space virtual address allocation; you might not see
a contiguous 3Gb chunk for malloc).
Kanoj
--
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/
prev parent reply other threads:[~2000-09-03 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-02 18:50 brian
2000-09-03 11:10 ` Stephen C. Tweedie
2000-09-03 17:26 ` Kanoj Sarcar [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=200009031726.KAA90541@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=brian@worldcontrol.com \
--cc=linux-kernel@vger.kernel.org \
--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