From: Keith Whitwell <keith@tungstengraphics.com>
To: Discuss issues related to the xorg tree <xorg@lists.freedesktop.org>
Cc: Brian Paul <brian.paul@tungstengraphics.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: State of Linux graphics
Date: Thu, 01 Sep 2005 18:26:42 +0100 [thread overview]
Message-ID: <431739D2.6060709@tungstengraphics.com> (raw)
In-Reply-To: <43173894.7040304@us.ibm.com>
Ian Romanick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Brian Paul wrote:
>
>
>>It's other (non-orientation) texture state I had in mind:
>>
>>- the texel format (OpenGL has over 30 possible texture formats).
>>- texture size and borders
>>- the filtering mode (linear, nearest, etc)
>>- coordinate wrap mode (clamp, repeat, etc)
>>- env/combine mode
>>- multi-texture state
>
>
> Which is why it's such a good target for code generation. You'd
> generate the texel fetch routine, use that to generate the wraped texel
> fetch routine, use that to generate the filtered texel fetch routine,
> use that to generate the env/combine routines.
>
> Once-upon-a-time I had the first part and some of the second part
> written. Doing just that little bit was slightly faster on a Pentium 3
> and slightly slower on a Pentium 4. I suspect the problem was that I
> wasn't caching the generated code smart enough, so it was it trashing
> the CPU cache. The other problem is that, in the absence of an
> assembler in Mesa, it was really painful to change the code stubs.
Note that the last part is now partially addressed at least - Mesa has
an integrated and simple runtime assembler for x86 and sse. There are
some missing pieces and rough edges, but it's working and useful as it
stands.
Keith
next prev parent reply other threads:[~2005-09-01 17:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 16:03 State of Linux graphics Jon Smirl
2005-08-30 17:26 ` David Reveman
2005-08-30 18:13 ` Jon Smirl
2005-08-30 22:38 ` Dave Airlie
2005-08-31 6:33 ` Allen Akin
2005-08-31 8:11 ` Anshuman Gholap
2005-08-31 17:20 ` David Reveman
2005-08-31 17:48 ` Jim Gettys
2005-08-31 18:23 ` Jon Smirl
2005-08-31 19:06 ` Allen Akin
2005-08-31 19:14 ` Jim Gettys
2005-08-31 18:29 ` Keith Packard
2005-08-31 20:06 ` Allen Akin
2005-08-31 20:20 ` Ian Romanick
2005-09-01 1:04 ` James Cloos
2005-08-31 21:06 ` Keith Packard
2005-09-01 1:58 ` Allen Akin
2005-09-01 3:11 ` Ian Romanick
2005-09-01 6:00 ` Antonio Vargas
2005-09-01 10:20 ` Alan Cox
2005-09-01 13:57 ` Antonio Vargas
2005-09-01 6:11 ` Allen Akin
2005-09-01 3:59 ` Keith Packard
2005-09-01 15:24 ` Brian Paul
2005-09-01 15:59 ` Jim Gettys
2005-09-01 16:39 ` Andreas Hauser
2005-09-01 20:18 ` Jim Gettys
2005-09-01 20:38 ` Jon Smirl
2005-09-01 21:29 ` Sean
2005-09-01 16:09 ` Alan Cox
2005-09-01 16:04 ` Brian Paul
2005-09-01 17:21 ` Ian Romanick
2005-09-01 17:26 ` Keith Whitwell [this message]
2005-09-01 20:03 ` Allen Akin
2005-08-31 3:11 ` Daniel Stone
2005-08-31 4:29 ` Jon Smirl
2005-08-31 4:50 ` Jon Smirl
[not found] ` <1125464500.8730.68.camel@localhost.localdomain>
2005-08-31 5:17 ` Jon Smirl
2005-08-31 5:23 ` Jon Smirl
2005-08-31 5:40 ` Jon Smirl
2005-08-31 6:15 ` Eric Anholt
2005-08-31 13:38 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2005-09-02 2:44 rep stsb
2005-09-03 4:00 mcartoaje
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431739D2.6060709@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=brian.paul@tungstengraphics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox