Re: Replacing init_alloc_aligned with a bitmapped allocator

2010-04-16 Thread Samuel Thibault
Karim Allah Ahmed, le Fri 16 Apr 2010 09:57:24 +0200, a écrit : > On 4/15/10, Samuel Thibault wrote: > >> - assert(init_alloc_aligned(round_page(len), &addr)); > >> + assert(init_alloc_aligned(kernel_cmdline_len, &addr)); > > > > This is not the same: init_alloc_aligned used to r

Re: Replacing init_alloc_aligned with a bitmapped allocator

2010-04-16 Thread Karim Allah Ahmed
On 4/15/10, Samuel Thibault wrote: >> -assert(init_alloc_aligned(round_page(len), &addr)); >> +assert(init_alloc_aligned(kernel_cmdline_len, &addr)); > > This is not the same: init_alloc_aligned used to required size aligned > on the page size. > i don't understand this one

Re: Replacing init_alloc_aligned with a bitmapped allocator

2010-04-14 Thread Samuel Thibault
Hello, Karim Allah Ahmed, le Wed 14 Apr 2010 13:11:05 +0200, a écrit : > The current "init_alloc_aligned" function will skip regions of memory > during an allocation if they aren't of "size" bytes of contigous > physical memory , and will never reclaim them later. ( it can't do > that with a simpl

Replacing init_alloc_aligned with a bitmapped allocator

2010-04-14 Thread Karim Allah Ahmed
The current "init_alloc_aligned" function will skip regions of memory during an allocation if they aren't of "size" bytes of contigous physical memory , and will never reclaim them later. ( it can't do that with a simple "available_next" ) In addition to the fact that it is unable to reserve any l