ProcPutImage calls exaDoMoveOutPixmap, 4x slowdown

[Michel Dänzer]

On Tue, 2008-10-14 at 16:02 +0200, Clemens Eisserer wrote:
> 
> I've a use-case where the client uploads 32x32 A8 images to an
> 256x256x8 pixmap  which is later used as mask in a composition
> operation.
> The test-case is able to render with 40fps on xserver-1.3/intel-2.1.1
> however with the latest GIT of both I only get ~10-15fps.
> Unfourtunatly I've not been able to create a stand-alone testcase
> which triggers this problem :-/
> 
> Using sysprof I can see a lot of time is spent moving data arround,
> very strange is that PutImage seems to cause a readback:
> ProcPutImage->ExaCheckPutImage->exaPrepareAccessReg->exaDoMigration->exaDoMoveOutPixmap->exaCopyDirty->exaWaitSync->I830EXASync
> In Composite I see the re-uploading again.
> 
> Any idea why ProcPutImage could to fallback (there's plenty of free vram)?
> Are there tools / settings which could help me to identify the problem?

Does the attached xserver patch help? Looks like we're syncing
unnecessarily in the migration no-op case.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: exa_migration.diff
Type: text/x-patch
Size: 926 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20081014/cdf2ee35/attachment.bin>