Pushing image transport logic down the stack

[Owen Taylor]

On Sun, 2006-09-03 at 23:50 +0100, Alan Cox wrote:
> Ar Sul, 2006-09-03 am 17:16 -0400, ysgrifennodd Owen Taylor:
> >  - A copy from and format conversion from your own data to the 
> >    shm buffer
> >  - A copy from the shm buffer onto the destination drawable
> 
> That's an X implementation limitation. Given kernel support it is
> perfectly possible to pin those pages and a kernel drive let a video
> card DMA those shm buffer pages.

I didn't specify whether the second copy above was being done by
the CPU or the video card ...

But really the question here is not "how low can you go" - but
rather, how can you go lower, while keeping the nice scheduling
and encapsulation properties of the X protocol?

I don't think the SHM extension really works out very well for
most applications once you take a broader view of success.

					 - Owen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20060903/aab95866/attachment.pgp>