Keith Whitwell wrote:
1) I think this is the first solution for memory management that I can
imagine implementing. Also it's one which gives reasonable
performance when data is being evicted from the GART.
This sounds a little trite reading it back.
This a function of two things, firstly that I've thought more about this
implementation than any other but also crucially that I've been able to find
straightforward answers to most of the problems that have come up about the
behaviour of the manager.
It seems to me that this could be implemented in a small to mid sized project
and beyond the extensions to the AGP module for map/unmapping doesn't have too
many scary implementation black holes.
It also seems like the drivers wouldn't change too drastically as a result of
adopting this memory manager.
I've not mentioned replacement algorithms at all as I feel that the design
doesn't place any constraints on the choice of replacement algorithm, pretty
much anything can be implemented inside of ValidateBuffer() and the rest of the
design would be unaffected.
Keith
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
