diff options
| -rw-r--r-- | xc/programs/Xserver/hw/dmx/doc/dmx.sgml | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/xc/programs/Xserver/hw/dmx/doc/dmx.sgml b/xc/programs/Xserver/hw/dmx/doc/dmx.sgml index 9590b99b3..12f910673 100644 --- a/xc/programs/Xserver/hw/dmx/doc/dmx.sgml +++ b/xc/programs/Xserver/hw/dmx/doc/dmx.sgml @@ -1639,13 +1639,13 @@ all optimizations individually and collectively. Note that some of the optimizations have a synergistic effect when used together. <verb> -2: XSync() batching only -3: Off screen optimizations only -4: Window optimizations only -5: Subdivprims only -6: All optimizations +1: XSync() batching only +2: Off screen optimizations only +3: Window optimizations only +4: Subdivprims only +5: All optimizations - 2 3 4 5 6 Operation + 1 2 3 4 5 Operation ------ ---- ---- ---- ------ --------- 2.14 1.85 1.00 1.00 4.13 Dot 1.67 1.80 1.00 1.00 3.31 1x1 rectangle @@ -1984,7 +1984,7 @@ that is similar to that provided by <tt/gprof/, but without the necessity of recompiling the program with special instrumentation (i.e., OProfile can collect statistical profiling information about optimized programs). A test harness was developed to collect OProfile data for -each <tt/x11perf/ test. +each <tt/x11perf/ test individually. <p>Test runs were performed using the RETIRED_INSNS counter on the AMD Athlon and the CPU_CLK_HALTED counter on the Intel Pentium III (with a @@ -1992,8 +1992,8 @@ test configuration different from the one described above). We are continuing to examine OProfile output and to compare it with <tt/gprof/ output. This investigation is ongoing and has not yet produced results that yield performance increases in <tt/x11perf/ numbers. However, we -will continue this investigation and provide addition information as -necessary. +will continue this investigation and provide addition information and +discussion as necessary. %<sect3>Retired Instructions @@ -2054,11 +2054,11 @@ XSetFontPath: Test 4 [1] XChangeKeyboardControl: Test 9, 10 [1] [1] Previously documented errors expected from the Xinerama - implementation (see Phase I discussion) + implementation (see Phase I discussion). [2] Newly noted errors that have been verified as expected - behavior of the Xinerama implementation + behavior of the Xinerama implementation. [3] Newly noted error that has been verified as a Xinerama - implementation bug + implementation bug. </verb> <!-- ============================================================ --> |