[Mesa-dev] [Bug 28415] New: Poor "direct rendering" choice with network GLX connection on DRI hardware

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28415

           Summary: Poor "direct rendering" choice with network GLX
                    connection on DRI hardware
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: GLX
        AssignedTo: mesa-dev at lists.freedesktop.org
        ReportedBy: andy at plausible.org


I hit a performance issue playing with Mesa running in a kvm guest (MeeGo 1.0,
as it happens).  TCP connections to the X server in the outer host were showing
very slow performance, and seemed to be highly fill limited on the VM where
they were not on the host (obviously transport bandwidth shouldn't change fill
rate for the same geometry), even on applications like glxgears which should be
almost identically performant.

Hacking at the glxgears source to set the "direct" parameter to FALSE restored
the performance characteristics I expected.

My guess as to what is happening here is that the presence of DRI drivers in
the both the guest OS and the target X server is fooling Mesa into interpreting
the "direct" parameter as possible, even when the server is on the other side
of a TCP socket and "direct" rendering must take a software path.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.