Skip to contentSkip to conversation

"3.5GB user address space" option.

DISCUSSION Oleg A. Yurlov 4 participants 5 messages Oct 17, 2001 – Oct 18, 2001

lore
Share & tools
lore
#0 lore raw

Hi, folks,

How I can use 3.5GB in my apps ? I try malloc() and get error on 2G
bounce... :-(

Hardware - SMP server, 2Gb RAM, 8Gb swap, kernel 2.4.12aa1.

--
Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
mailto:[email protected] +7 095 332-03-88

#1 lore raw
Quoted 2 lines · Oleg A. Yurlov

How I can use 3.5GB in my apps ? I try malloc() and get
error on 2G bounce... :-(

You may want to use the 'hoard' memory allocation library, it seems a bit smarter than glibc's malloc in getting all the address space your program wants.

1) install libhoard
2) export LD_PRELOAD=libhoard.so
3) run the program

cheers,

Rik

Signature · 3 lines
DMCA, SSSCA, W3C?  Who cares?  http://thefreeworld.net/  (volunteers needed)

http://www.surriel.com/		http://distro.conectiva.com/
#2 lore raw
In reply to Oleg A. Yurlov
Followup to:  <[email protected]>
By author:    "Oleg A. Yurlov" <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 9 lines

Hi, folks,

How I can use 3.5GB in my apps ? I try malloc() and get error on 2G
bounce... :-(

Hardware - SMP server, 2Gb RAM, 8Gb swap, kernel 2.4.12aa1.

Get a 64-bit CPU. You're running into a fundamental limit of 32-bit architectures.

-hpa

Signature · 3 lines
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<[email protected]>
#3 lore raw
In reply to Oleg A. Yurlov
Quoted 7 lines · H. Peter Anvin
Followup to:  <[email protected]>
By author:    "Oleg A. Yurlov" <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 4 lines

Hi, folks,

Quoted 8 lines
Quoted 5 lines

How I can use 3.5GB in my apps ? I try malloc() and get error on 2G
bounce... :-(

Hardware - SMP server, 2Gb RAM, 8Gb swap, kernel 2.4.12aa1.

Get a 64-bit CPU. You're running into a fundamental limit of 32-bit architectures.

Actually 3.5G per-process is theoretically possible using a careful userspace as Rik suggested with -aa after enabling the proper compile time configuration option. So for apps that needs say 3G per-process it should work just fine. But of course for anything that needs more than that 64bit is the right way to go :)

Andrea

#4 lore raw
        Hi,

Thursday, October 18, 2001, 1:09:14 PM, you wrote:

Quoted 7 lines · H. Peter Anvin
Quoted 7 lines
Followup to:  <[email protected]>
By author:    "Oleg A. Yurlov" <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 4 lines

Hi, folks,

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines

How I can use 3.5GB in my apps ? I try malloc() and get error on 2G
bounce... :-(

Hardware - SMP server, 2Gb RAM, 8Gb swap, kernel 2.4.12aa1.

Get a 64-bit CPU. You're running into a fundamental limit of 32-bit architectures.

AA> Actually 3.5G per-process is theoretically possible using a careful AA> userspace as Rik suggested with -aa after enabling the proper AA> compile time configuration option. So for apps that needs say 3G AA> per-process it should work just fine. But of course for anything that AA> needs more than that 64bit is the right way to go :)

Thanks to all, problem solved :-) Now apps can use about 3.5G.

AA> Andrea
AA> -
AA> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in AA> the body of a message to [email protected]
AA> More majordomo info at http://vger.kernel.org/majordomo-info.html
AA> Please read the FAQ at http://www.tux.org/lkml/

--
Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
mailto:[email protected] +7 095 332-03-88