From: jansen <jansen@astro.wisc.edu>
To: linux-mm@kvack.org
Subject: Problems accessing > 2GB RAM per process
Date: Fri, 01 Dec 2000 14:28:41 -0600 [thread overview]
Message-ID: <3A2809F9.C3360160@astro.wisc.edu> (raw)
Hi,
I have just gotten a Intel Linux box with 4GB of RAM and am
having problems accessing more than 2 GB of RAM in a single
process. I am using 2.2.18pre11-va1.1smp on a VA Linux machine
which has the BIGMEM stuff compiled in, and I'm currently using
the RedHat 7.0 (and updated) gcc and glibc stuff installed (ie:
binutils-2.10.0.18-1,gcc-2.96-54, kgcc-1.1.2-40, gcc-g77-2.96-54,
glibc-devel-2.2-5, glibc-2.2-5). I'm compiling simple test
programs in C and Fortran with "-static" and still I can't access
RAM beyond 2GB (it was about 1.5 GB without the "-static" switch).
The symptom is a SEGV when accessing an array in Fortran and in
C I am unable to malloc beyond 2GB. Any suggestions on what I'm
doing wrong?
Is there any way to access more than 3 GB per process with this
setup and if so how?
Thanks and sorry if this is FAQ, I couldn't find this adequately
answered anywhere.
Here's what it says in meminfo:
#cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 4160315392 406388736 3753926656 0 71380992 233754624
Swap: 4293509120 0 4293509120
MemTotal: 4062808 kB
MemFree: 3665944 kB
MemShared: 0 kB
Buffers: 69708 kB
Cached: 228276 kB
BigTotal: 3080188 kB
BigFree: 3051196 kB
SwapTotal: 4192880 kB
SwapFree: 4192880 kB
--
------- Stephan
--
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 reply other threads:[~2000-12-01 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 20:28 jansen [this message]
2000-12-01 20:59 ` afei
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=3A2809F9.C3360160@astro.wisc.edu \
--to=jansen@astro.wisc.edu \
--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