Re: radeon, apertures & memory mapping

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

> AGP as it's currently used is pretty much pointless for software fallbacks 
> since reading from AGP memory is nearly as slow as reading from video 
> memory.

Hrm.. I wouldn't expect _that_ slow. It's uncacheable, right, but still
on a faster bus. Especially if we use it the way we do on ppc where we
actually map the RAM pages directly instead of having processes go
through the GART.

> > Or things can be put in accessible space,
> > and blitted elsewhere using the accelerator.
> 
> This could work (and it would avoid DRM which in my book is a plus) but 
> it's not very nice to have to copy the data twice.
> 
> > That "half" of vram is plenty enough for a framebuffer (and more). it's
> > only an issue when you start doing very large offscreen surfaces. Do you
> > have much usage of those without DMA ?
> 
> I have about 26MB of video memory used when running XDirectFB with GNOME, 
> epiphany and 4 gnome-terminals, and I also have some videos playing on the 
> TV at the same time. That's on a 32MB G400 BTW.
> 
> I must be missing something something obvious because I don't quite 
> understand what major drawbacks there are with the non-overlapping mode. 
> As I see it you get at least the same amount of CPU accessible memory as 
> you get in the overlapping mode.

Yes, you do, but that means that if the apertures are configured such
that the entire VRAM fits in a single aperture, then you just can't use
the second aperture at all. Which means you can't have separate swapper
setting for both apertures, and thus, can't let two independant
processes access the video memory with different bit depth, at least on
big endian machines unless you do trickery, and play with the swapper
before each access.

Ben.