Sven Luther wrote:
On Thu, Jan 16, 2003 at 05:33:42PM -0800, Ian Romanick wrote:

1. Single-copy textures

Right now each texture exists in two or three places. There is a copy in on-card or AGP memory, in system memory (managed by the driver), and in application memory. Any solution should be able to eliminate one or two of those copies.
...

BTW, since you are looking into this, have you thought about graphic
chips which can do MMU like tricks. I am not sure if the current set of
graphic chips the DRI runs on do this kind of stuff, but they well may
in the future. I know the gamma drm module use the gamma's virtual
memory table to not need to do virtual<->physical conversion. But more
importantly to you, altough there is not yet a DRI driver for it, the
3Dlabs permedia3 can use virtual memory for its textures. That is you
can basically set up the graphic boards memory as a cache memory, and
have the the MMU-like unit swap the memory pages from host memory, using
i suppose its own page replacement algorithm.
The only chips that I know of that support this technology are the various, recent 3dlabs chips. They have a number of patents on this technology, and, AFAIK, they have no intention of licensing it to anyone for all the tea in China.

I agree that it is a good idea to keep virtual textures in mind, but, since we don't have any hardware documentation for it, it will be difficult to do more than that.



-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to