Re: Implementing a custom memory allocator
- From: "Don Burn" <burn@xxxxxxxxxxxxxxxx>
- Date: Thu, 3 Aug 2006 08:20:44 -0400
"anton bassov" <soviet_bloke@xxxxxxxxxxx> wrote in message
I would say that all the above are just application-level
memory-management strategies - none of them seems to qualify for being
a real "custom memory allocator", don't you think????
Anton,
Then what is a "custom memory allocator", you can't do anything else
unless you really hack the kernel (oop's I forgot you recomend such
stupidity). Even the heap is just a layer over the allocate memory calls
from the system.
This is perfectly valid and is a memory manager. In fact under the
right circumstances this is a valid thing to do in the kernel as well as
user space.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
.
- Follow-Ups:
- Re: Implementing a custom memory allocator
- From: anton bassov
- Re: Implementing a custom memory allocator
- From: adebaene
- Re: Implementing a custom memory allocator
- References:
- Implementing a custom memory allocator
- From: Ranjit
- Re: Implementing a custom memory allocator
- From: adebaene
- Re: Implementing a custom memory allocator
- From: anton bassov
- Implementing a custom memory allocator
- Prev by Date: Re: Implementing a custom memory allocator
- Next by Date: Re: CreateFile executable file types
- Previous by thread: Re: Implementing a custom memory allocator
- Next by thread: Re: Implementing a custom memory allocator
- Index(es):
Relevant Pages
|