Go to the FreeLists Home Page Home Signup Help Login
 



Browse haiku: This Month's ArchiveMain Archive PageRelated postsPrevious by DateNext by Date

[openbeos] Re: kernel memory limit

  • From: François Revol <revol@xxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Mon, 02 Jun 2003 12:55:36 +0200 (CEST)
En réponse à Bruno van Dooren <bruno_van_dooren@xxxxxxxxxxx>:

> 
> > No, NewOS doesn't map all available memory - that's a BeOS only
> > feature, and is responsible for this hard limit; neither NewOS nor
> > OpenBeOS have it.
I stand corrected.

> 
> what do you mean by this?
> i thought memory was allocated on a by-need basis, and that for example
> all
> PCI memory is mapped in an unused region > xxx GB.
> 
> i think i do not understand what you mean by mapping.
> 
> kind regards,

At boot, the BeOS kernel does the equivalent of:

map_physical_memory("physical_ram", 0, PHYS_SIZE, ...);

So it "wastes" its 2G virtual space by creating an area that is as big 
as the physical RAM...

Just check yourself:

listarea 1 | head -25


François.

Other related posts:

  • [openbeos] kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit
  • [openbeos] Re: kernel memory limit




  • [ Home | Signup | Help | Login | Archives | Lists ]

    All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
    Everything else ©2008 Avenir Technologies, LLC.