Bug 6221

Summary: Major performance loss compared to 6.9.0
Product: xorg Reporter: Lukas Hejtmanek <xhejtman>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED DUPLICATE QA Contact:
Severity: critical    
Priority: high    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Lukas Hejtmanek 2006-03-11 06:43:21 UTC
I tried to compile current CVS HEAD of X.org 7.0.0. I have intel i915 graphic card.

Using glxgears I got 600 FPS with 7.0.0 and 1100 FPS using 6.9.0.
Using x11perf -shmput500 I got 105 FPS with 7.0.0 and 1400 FPS using 6.9.0.

I tried to combine X server 7.0.0. and i810_drv from 6.9.0, it's the same.
I tried to combine X server 7.0.0. and X libs from 6.9.0, it's the same.
I tried to disable the composite extension, it's the same.
Comment 1 Lukas Hejtmanek 2006-03-13 08:44:04 UTC
Problems with 2D graphic causes bug in configure.ac in xserver/xorg package that
for Linux does not define HAS_MTRR_SUPPORT.

Problems with 3D remain.
Comment 2 Lukas Hejtmanek 2006-03-23 10:31:35 UTC
(In reply to comment #1)
> Problems with 2D graphic causes bug in configure.ac in xserver/xorg package that
> for Linux does not define HAS_MTRR_SUPPORT.
> 
> Problems with 3D remain.

Patch for configure.ac:
--- configure.ac        2006-03-09 15:23:57.000000000 +0100
+++ configure.ac.new    2006-03-23 00:30:21.000000000 +0100
@@ -115,7 +115,11 @@
 AM_CONDITIONAL(FBDEVHW, [test "x$FBDEV" = xyes])
 
 dnl MTRR header
-AC_CHECK_HEADERS([asm/mtrr.h])
+AC_CHECK_HEADERS([asm/mtrr.h], ac_cv_mtrr_h=yes)
+if test "x$ac_cv_mtrr_h" = xyes; then
+        AC_DEFINE(HAS_MTRR_SUPPORT, 1, [Define to 1 if Linux MTRR support is
+                 available])
+fi
 
 dnl BSD MTRR header
 AC_CHECK_HEADERS([sys/memrange.h], ac_cv_memrange_h=yes)
Comment 3 Daniel Stone 2006-04-02 07:18:58 UTC

*** This bug has been marked as a duplicate of 5801 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.