1978 called, wants its garbage collectors back
Posted Sep 4, 2008 17:12 UTC (Thu) by BrucePerens
In reply to: 1978 called, wants its garbage collectors back
Parent article: The Kernel Hacker's Bookshelf: UNIX Internals
Is there not a case where you're freeing up blocks "deterministically" and then the block you just freed happens to complete a large hole and kfree/free suddenly goes off and does a lot of work to update its internal structures?
I don't see how GC would improve that situation. It's reasonably trivial to code a kernel allocator that doesn't go into some loosely-bounded task at interrupt level.
GC has its own errors, especially if it's the kind that assumes any word might be a pointer.
to post comments)