From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Hartmut Manz <manz@intes.de>, linux-kernel@vger.kernel.org
Subject: Re: allocate more than 2 GB on IA32
Date: Tue, 11 Feb 2003 18:21:34 +0100 [thread overview]
Message-ID: <3E49311E.6090108@colorfullife.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Martin wrote:
>> i would like to allocate more than 2 GB of memory on an IA32 architecture.
>>
>> The machine is a dual XEON_DP with 3 GB of Ram and 4 GB of swap space.
>>
>> I have tried with the default SUSE 8.1 kernel as well as with a
>> 2.4.20-pre4aa1 Kernel compile by my own using these Options:
>>
>> CONFIG_HIGHMEM4G=y
>> CONFIG_HIGHMEM=y
>> CONFIG_1GB=y
>>
>> but I am only able to allocate 2 GB with a single malloc call.
>> I tought it should be possible to allocate up to 2.9 GB of memory to a
>> process, with this kernel settings.
>
>Well, assuming you had no user-space code or data, or a stack, or any
>shared libraries to fit into that space as well ;-)
>
>
It's tricky, but not impossible.
Hartmut, start you application, allocate 2 gigabyte memory and then check
/proc/<pidof your app>/maps.
It shows how your virtual memory is used.
You application is loaded at address 0x08000000. The stack is at
0xbfffxxxx. Addresses above 0xC0000000 are reserved for the kernel.
Usually shared libraries are loaded at 0x40000000, and thus the largest
area is 2 GB: from 0x400xxxx to 0xbfffxxxx.
You must remove everything that is at 0x4000xxxx, then you can malloc
2.9 GB. Linking with --static is definitively required, but it's not
enough - the glibc-2.3 library startup seems to malloc something at
0x40000000. Try another C library.
One alternative would be a 2.9 GB global variable. An ugly example is
attached - I could create a 2943 MB large variable.
With some asm-foo, it should be possible to create one 2.9 GB variable.
Then implement your own malloc, backed by that 2.9 GB memory area.
--
Manfred
[-- Attachment #2: testmalloc.c --]
[-- Type: text/plain, Size: 622 bytes --]
#include <malloc.h>
// Test the maximum size of one linear block that is achievable with Linux
// compile with gcc --static.
#define SIZE 2943
unsigned char dummy1[1024UL*1024*SIZE/2];
unsigned char dummy2[1024UL*1024*SIZE/2];
int main(void)
{
if ((unsigned long)dummy2 != (unsigned long) ((&dummy1)+1)) {
printf("dummy1 has address %lx, ends at %lxh.\n",dummy1, (&dummy1)+1);
printf("dummy2 has address %lx.\n",dummy2);
printf("duh. something went wrong.\n");
} else {
printf("%d MB memory block starting at address %lxh available.\n",
SIZE, (unsigned long)dummy1);
}
for(;;) sleep(100);
return 0;
}
next reply other threads:[~2003-02-11 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 17:21 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-11 9:15 allocate more than 2 GB on IA32 Hartmut Manz
2003-02-11 9:31 ` Gianni Tedesco
2003-02-11 9:33 ` ÷ÉÔÁÌÉÊ
2003-02-11 16:11 ` Martin J. Bligh
2003-02-20 17:40 ` Hartmut Manz
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=3E49311E.6090108@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manz@intes.de \
--cc=mbligh@aracnet.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