dmx/doc/dmx.xml

104 describes the four phases of development that were performed during the
110 that time were the enhancement of the reconfiguration ability added in
217         drivers, the <command>kdrive</command> drivers were not used for the DMX
226         selected.  Other drivers in the X source tree were referenced,
263     <para>Other options were initially explored, but they were all
273 Distributed X requirements, the options above were all implemented so
274 that XInput extension devices were supported.
285 infrastructure), separate low-level device drivers were implemented for
442     were implemented to eliminate the drawbacks of the default
879 core pointer device were registered and successfully enabled.  If not,
1068 specific data structures were allocated when the device was initialized,
1074 <para>CloseDevice() then frees the data structures that were allocated
1177 below.  It returns the number of the screen that were just added, or -1
1337 arguments that were passed into it.  Other GCOps functions are very
1533     FALSE if no common depths were found in PanoramiXConsolidate().
1543     values that were calculated in the above two functions.
1830               These failures were noted with multiple Xinerama
1840               These failures were noted only when using one dual-head
1848               These failures were noted only when using two video cards
1865               When running Xdmx, no unexpected failures were noted.
1960 the Xdmx server.  However, several insights were gained during Phase I,
1982 <para>Pixmaps were originally expected to be handled entirely in the
2006 <para>All benchmarks were performed by running Xdmx on a dual processor
2010 2.4.20-pre1-ac1 and the back ends were running Linux 2.4.7-10 and
2012 August 7, 2002.  All systems were running Red Hat Linux 7.2.
2021 After this update, the following tests were noted to be more than 10%
2033 And the following tests were noted to be more than 10% slower:
2044 <para>These changes were not caused by any changes in the DMX system, and
2054 changes were made.  These changes were also compared with the Phase I
2055 server.  The following tests were noted to be more than 10% faster:
2068 <para>The following tests were noted to be more than 10% slower:
2106 <para>The following tests were noted to be more than 10% slower with
2119 during Phase I development, windows were created on every back-end
2126 XSync() calls.  The performance tests were run on a DMX system with only
2131 <para>Out of more than 300 <command>x11perf</command> tests, 3 tests were at least twice as
2132 fast, and 146 tests were at least 10% faster.  Two tests were more than
2144 <para>As mentioned above, during Phase I, windows were created on every
2145 back-end server even if they were not visible on that back-end.  With
2180 because it increased bandwidth when windows were opaquely moved or
2184 <para>The performance tests were run on a DMX system with only two back-end
2221 <para>Other rendering primitives were analyzed, but the time required to
2227 <para>Again, the performance tests were run on a DMX system with only two
2261 No tests were more than 10% slower than the unoptimized Phase II
2624 <para>Test runs were performed using the RETIRED_INSNS counter on the AMD
2637 <p>The initial tests using OProfile were done using the RETIRED_INSNS
2659 execute in variable amounts of time.  The OProfile tests were repeated
2665 window optimizations were on, the load on the second back-end machine
2675 <p>The trapezoid, text, scrolling, copying, and image tests were
2686 configuration described above.  The following failures were noted:
2902 <para>The XTEST and RECORD extension were developed by the X Consortium for
3115 were reported from Xdmx (note that these are the same as for the XFree86
3135 were reported from Xdmx:
3165 were reported from Xdmx (these results are from early during the Phase
3166 IV development, but were confirmed with a late Phase IV snapshot):
3189 over the entire set of visuals, additional rendering tests were run and
3331 search for memory management errors.  Several memory leaks were detected
3332 and repaired.  The following errors were not addressed:
3338         noted by valgrind.  These instances are not errors and were not
3370 and all "High" notations were checked manually.  The code was either