Paul
Tue Sep 23 12:20:59 CDT 2003
To be more specific, you can check the source, assuming you've installed it,
at \WINCE420\PRIVATE\WINCEOS\COREOS\CORE\LMEM.
There's also a 'debugging' tool that you can build into the OS, LMEMDEBUG,
which allows you to see what allocations are being done. You can find this
at \WINCE420\PUBLIC\COMMON\OAK\DRIVERS\LMEMDEBUG. The readme file in that
directory has some more information, also.
If you are writing something that must run real-time, it would be a good
idea to pre-allocate a block of memory large enough for all of your
allocations for the life of the real-time process and use a real-time
suballocation algorithm to handle allocations/deallocations yourself. Since
the OS itself has to worry about a lot of things that might happen, it has
to be very general-purpose and you can probably do better, since you know
more about the real situation.
Paul T.
<hel@40th.com> wrote in message
news:epuZVRfgDHA.2072@TK2MSFTNGP10.phx.gbl...
> Use the source, luke. It's all there. Of course, if you listen
> to the likes of sloh and pt, you can't comment on it here -- but
> don't listen to them, not anymore than you'd take driving leasons
> from the nutcase tailgating you at 70 mph on the off-ramp.
>
> YDLU [23 Sep 2003 09:47:28 -0700]:
> >Does anyone known what kind of algorithm used on CE.NET for memory
> >allocation, best-to-fit or some one else?
>
> But don't go here
>
>
http://www.theregister.co.uk/content/7/28724.html
>
> because it shows how busy The Lawyers are. CE.NET, you mean 4.2?
>
> --
> 40th Floor - Software @
http://40th.com/
> GT40 encryption-database toolkit
>