Re: Reserving a (large) memory block

From: Timur Tabi (ttabi@interactivesi.com)
Date: Thu Aug 31 2000 - 12:30:02 EDT

Next message: Christoph Rohland: "Re: /proc/sys/kernel/shmmax does not increase shared ram"

Previous message: Jeff V. Merkey: "NWFS sb->s_blocksize issues"
In reply to: Ingo Molnar: "Re: Reserving a (large) memory block"
Next in thread: coder@kanga.nu: "Re: Reserving a (large) memory block"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

** Reply to message from Ingo Molnar <mingo@elte.hu> on Thu, 31 Aug 2000
14:09:48 +0200 (CEST)

> in 2.4 there is an explicit interface for this that also guarantees that
> the allocation consists of fully valid RAM (no matter how complex the RAM
> map): alloc_bootmem(). We allocate 300MB+ worth of mem_map[] with this on
> multi-gigabyte boxes.

Could you explain this API in more detail, I'm having a hard time following the
code. Can this API be called by drivers at any time? I don't see how this API
is different than a normal kmalloc().

-- Timur Tabi - ttabi@interactivesi.com Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please don't cc: me, because then I'll just get two copies of the same message. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/

Next message: Christoph Rohland: "Re: /proc/sys/kernel/shmmax does not increase shared ram"
Previous message: Jeff V. Merkey: "NWFS sb->s_blocksize issues"
In reply to: Ingo Molnar: "Re: Reserving a (large) memory block"
Next in thread: coder@kanga.nu: "Re: Reserving a (large) memory block"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 12:27:04 EDT