Lines Matching +full:high +full:- +full:performance

5 --------------------------------
10  * Architecture - given our focus on scientific visualization, our
16  * Historical - Intel had developed a high performance software
19    with Mesa to provide a high quality API layer while at the same
20    time benefiting from the excellent performance the software
24 ------------------------
26 SWR is a tile based immediate mode renderer with a sort-free threading
36 Our pipeline uses just-in-time compiled code for the fetch shader that
46 What's the performance?
47 -----------------------
49 For the types of high-geometry workloads we're interested in, we are
52 frontend.  The performance advantage over llvmpipe roughly scales
55 While our current performance is quite good, we know there is more
57 OpenGL driver to Mesa we regressed performance severely, some due to
60 core swr.  We are looking to recovering most of this performance back.
63 -----------------------
81 -------------------------------
94 --------------------------------
96  * Performance - see the performance section earlier for details.
98  * Conformance - see the conformance section earlier for details.
100  * Features - core SWR has a lot of functionality we have yet to
107 ----------------------------------
112 ----------------------
118 Will this work on ARM, MIPS, POWER, <other non-x86 architecture>?
119 -------------------------------------------------------------------------
122    intrinsics in our code and the in-tree JIT creation.  It is not the
123    intention for this codebase to support non-x86 architectures.
126 ------------------------
132  * You don't need a fire-breathing Xeon machine to work on SWR - we do
133    day-to-day development with laptops and desktop CPUs.
136 -----------------------------------------