--- 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.
There was one posted after that. It was posted on 3-Mar-2003. For some reason, the attachment isn't on marc.
http://marc.theaimsgroup.com/?l=dri-devel&m=104673516801006&w=2
Since that point the design has changed some, but the document has not. I started writing a simulation of the design using pthreads. Some actual implementation experience exposed some problems in the design. Looking that the modification times on the files, I haven't worked on any of it since 27-May-2003.
I *did* start looking at it again today. :)
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.
That's a good question. I'd probably have to talk to someone that knows better what is available in the kernel.
Are there any more design documents like this floating around that should be referenced?
-------------------------------------------------------
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
