On Tue, 20 Nov 2001, Mike A. Harris wrote:
> konsole, mozilla, any other application that is maximized. You
> name it. I can watch it draw the whole screen and count out
> loud.
>
> In 1600x1200x24 It takes 1 full second to draw the screen, or a
> good 3/4 of a second. That is definitely not accelerated.
> Again, disabling DRI, the MMIO accel makes everything fly.
> >I've seen DRI slow 2D down to a "crawl", but that's only been
> >in memory limited situations where there isn't enough remaining
> >offscreen memory for pixmaps, so drawing to them isn't accelerated
> >at all. (Not even CopyArea and solid fills.)
>
> 64Mb DDR Radeon here, and 1Gb of system RAM. AGP aperture set to
> 64Mb, and AGP 2x is being used. MTRR not functional on
> serverworks.
I haven't looked hard at the radeon code, but the matrox DRI
grabs as much memory as possible - mga_driver.c includes the comment
/* If that gives us less than half the available memory, let's
* be greedy and grab some more. Sorry, I care more about 3D
* performance than playing nicely, and you'll get around a full
* framebuffer's worth of pixmap cache anyway.
*/
If that is the general attitude of DRI developers, no wonder you have a
problem.
Is Mozilla as profligate with pixmaps as Netscape 4 ?
At that resolution each pixmap needs nearly 6 meg, and Netscape 4 seemed
able to use half a dozen pixmaps the size of the window.
If DRI uses half the Video RAM for 3D, you could still
be running out for 2D.
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
