--- Ian Romanick <[EMAIL PROTECTED]> wrote: > That's not entirely true. I made a proposal last February (search the > dri-devel archives for "texmem-0-0-2") that used a combination of > in-kernel and user-space. Basically, the memory management mechanism is > implemented in-kernel, but the policy is implemented in user-space.
Here's a link to it: http://www.mail-archive.com/[EMAIL PROTECTED]/msg09472.html Do you have any updates to it? We can put a copy up on fd.o and I'll link it into the next round of discussions. Can any of the kernel memory management code be reused instead of building our own? Obviously this is a different pool but maybe we could use existing allocators. Are there any more design documents like this floating around that should be referenced? ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
