public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* "3.5GB user address space" option.
@ 2001-10-17 22:18 Oleg A. Yurlov
  2001-10-17 22:27 ` Rik van Riel
  2001-10-18  4:38 ` H. Peter Anvin
  0 siblings, 2 replies; 5+ messages in thread
From: Oleg A. Yurlov @ 2001-10-17 22:18 UTC (permalink / raw)
  To: linux-kernel, mantel


        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:kris@spylog.com                          +7 095 332-03-88


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "3.5GB user address space" option.
  2001-10-17 22:18 "3.5GB user address space" option Oleg A. Yurlov
@ 2001-10-17 22:27 ` Rik van Riel
  2001-10-18  4:38 ` H. Peter Anvin
  1 sibling, 0 replies; 5+ messages in thread
From: Rik van Riel @ 2001-10-17 22:27 UTC (permalink / raw)
  To: Oleg A. Yurlov; +Cc: linux-kernel, mantel

On Thu, 18 Oct 2001, Oleg A. Yurlov wrote:

>         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
-- 
DMCA, SSSCA, W3C?  Who cares?  http://thefreeworld.net/  (volunteers needed)

http://www.surriel.com/		http://distro.conectiva.com/


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "3.5GB user address space" option.
  2001-10-17 22:18 "3.5GB user address space" option Oleg A. Yurlov
  2001-10-17 22:27 ` Rik van Riel
@ 2001-10-18  4:38 ` H. Peter Anvin
  2001-10-18  9:09   ` Andrea Arcangeli
  1 sibling, 1 reply; 5+ messages in thread
From: H. Peter Anvin @ 2001-10-18  4:38 UTC (permalink / raw)
  To: linux-kernel

Followup to:  <1981072193242.20011018021819@spylog.com>
By author:    "Oleg A. Yurlov" <kris@spylog.com>
In newsgroup: linux.dev.kernel
>
> 
>         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
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "3.5GB user address space" option.
  2001-10-18  4:38 ` H. Peter Anvin
@ 2001-10-18  9:09   ` Andrea Arcangeli
  2001-10-18 13:47     ` Re[2]: " Oleg A. Yurlov
  0 siblings, 1 reply; 5+ messages in thread
From: Andrea Arcangeli @ 2001-10-18  9:09 UTC (permalink / raw)
  To: H. Peter Anvin; +Cc: linux-kernel

On Wed, Oct 17, 2001 at 09:38:35PM -0700, H. Peter Anvin wrote:
> Followup to:  <1981072193242.20011018021819@spylog.com>
> By author:    "Oleg A. Yurlov" <kris@spylog.com>
> In newsgroup: linux.dev.kernel
> >
> > 
> >         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.

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re[2]: "3.5GB user address space" option.
  2001-10-18  9:09   ` Andrea Arcangeli
@ 2001-10-18 13:47     ` Oleg A. Yurlov
  0 siblings, 0 replies; 5+ messages in thread
From: Oleg A. Yurlov @ 2001-10-18 13:47 UTC (permalink / raw)
  To: Andrea Arcangeli; +Cc: H. Peter Anvin, linux-kernel


        Hi,

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

AA> On Wed, Oct 17, 2001 at 09:38:35PM -0700, H. Peter Anvin wrote:
>> Followup to:  <1981072193242.20011018021819@spylog.com>
>> By author:    "Oleg A. Yurlov" <kris@spylog.com>
>> In newsgroup: linux.dev.kernel
>> >
>> > 
>> >         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.

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 majordomo@vger.kernel.org
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:kris@spylog.com                          +7 095 332-03-88


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-10-18 13:51 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-17 22:18 "3.5GB user address space" option Oleg A. Yurlov
2001-10-17 22:27 ` Rik van Riel
2001-10-18  4:38 ` H. Peter Anvin
2001-10-18  9:09   ` Andrea Arcangeli
2001-10-18 13:47     ` Re[2]: " Oleg A. Yurlov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox