[ros-dev] Re: [ros-svn] [ion] 15492: Nonpaged Pool Liberation Day: Allow PagedPool to be used earlier, allow fast mutex to be used earlier on debug builds. Allocate all Se stuff from PagedPool, set the right object types to use paged pool, allocate all strings from paged pool, allocate PE sections from paged pool, and a bunch of other things which should, imo, be in paged pool. If anyone has any contradicting proof, let me know...until then, enjoy ~4-6MB more NonPagedPool

[Hartmut Birr]

ion(a)svn.reactos.com wrote:

>  Nonpaged Pool Liberation Day: Allow PagedPool to be
> used earlier, allow fast mutex to be used earlier on debug builds. Allocate all Se stuff
> from PagedPool, set the right object types to use paged pool, allocate all strings from
> paged pool, allocate PE sections from paged pool, and a bunch of other things which
> should, imo, be in paged pool. If anyone has any contradicting proof, let me know...until
> then, enjoy ~4-6MB more NonPagedPool
>
>
>   
>  
Hi,

I don't like the exchange from NonPagedPool to PagePool at the current
state of ros. There are two reasons: 

A) The allocation of paged pool is very slowly compared with the non
paged pool allocation.

B) Since the change to the new object type structures, ros has a big
memory leakage in the memory (pool) allocation/deallocation of objects.
For the non paged pool, there exist some debug functions to find the
problem. The paged pool doesn't implement anything to find such problems.

- Hartmut