On 9/25/07, William Lahti <[EMAIL PROTECTED]> wrote: > Erm, hey Sander I've got a bunch of memory management code in my > sandbox.... It covers page allocation, buffer allocation (malloc), > paging (broken), and garbage collection.
I didn't know, i only looked at what was in the kernel.. > On 9/25/07, Sander van Rossen <[EMAIL PROTECTED]> wrote: > > I build a memory manager (it's in ADC.MemoryManager) with which you > > can allocate/release memory.. > > It doesn't use any paging (It could/should be merged with the paging > > code from xfury at some point), but i think that, for now, this will > > be fine to start building some things like vtables.. > > It did some quick tests, fixed some bugs, and it seems to work fine > > now (but don't be too suprised if you find a bug) > > What technique does it use? Mine uses stack-based allocation like NT > and Linux, thats where the memory manager stores a stack of every free > page, and pops a value off the stack to allocate and back on to > deallocate. It's more efficient than bitmap. I have two linked lists, one with 'empty' nodes and one with used nodes. It merges empty nodes when adjacent nodes are empty etc. It's pretty simple. Honestly, I haven't put much tought into paging because i consider this to be temp. code anyway untill we get to the point where we can implement garbage collection.. But we can replace it with your code, it seems to be more advanced, no problem to me.. Too bad i waisted my time on this ;) How much work would it cost to get it operational? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
