lkml.org 
[lkml]   [1999]   [Apr]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2GB malloc impossible ?
Hi Alexander.

> I'm trying to allocate 2GB of Physical memory from user program.
> (I do have that much so I use 2:2 split of address spaces).

> The fact is that malloc'ing more than 1.3G results in ENOMEM. I
> tried to track the problem down and found that mmap wants to map
> desired region starting from something like 0x2aaab000. No
> wonder it couldn't map more than 0x80000000 - 0x2aaab000 bytes.

> I have no idea about where 0x2aaab000 has come from, but I am
> eager to know. If anybody has the solution, or any suggestions,
> please, let me know.

If you're going to allocate your entire 2G of ram as a program data
area, where do you expect the program to live - or the kernel itself,
come to that?

I would suspect that's the space occupied by the kernel image and
whatever programs you're running at the time...

Best wishes from Riley.

+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.392 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site