From: Keith Packard <keithp@keithp.com>
To: Eric Anholt <eric@anholt.net>, Ben Widawsky <ben@bwidawsk.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] [RFC] drm/i915: read-read semaphore optimization
Date: Tue, 13 Dec 2011 19:25:46 -0800 [thread overview]
Message-ID: <8639cnj0lh.fsf@sumi.keithp.com> (raw)
In-Reply-To: <87fwgoq7qe.fsf@eliezer.anholt.net>
[-- Attachment #1.1: Type: text/plain, Size: 541 bytes --]
On Tue, 13 Dec 2011 17:09:45 -0800, Eric Anholt <eric@anholt.net> wrote:
> We introduced this complexity with no evidence that it would help, just
> because we thought, like you, that "avoiding cache flushes should be
> good, right?". Experiments so far say we were wrong.
Right, you'd think we'd have learned to not optimize in advance of
data. Someday maybe we'll know better...
And, of course, future hardware may require different code for optimal
performance. Who would have guessed that?
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-12-14 3:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 3:52 [PATCH] [RFC] drm/i915: read-read semaphore optimization Ben Widawsky
2011-12-13 9:49 ` Chris Wilson
2011-12-13 16:01 ` Daniel Vetter
2011-12-13 16:36 ` Keith Packard
2011-12-13 22:49 ` Ben Widawsky
2011-12-13 23:22 ` Keith Packard
2011-12-14 1:09 ` Eric Anholt
2011-12-14 3:25 ` Keith Packard [this message]
2011-12-13 16:59 ` Chris Wilson
2011-12-13 17:22 ` Eric Anholt
2011-12-13 18:36 ` Ben Widawsky
2012-01-16 21:50 ` Daniel Vetter
2012-01-16 22:20 ` Ben Widawsky
2012-01-17 3:41 ` Eric Anholt
2012-01-17 10:15 ` Daniel Vetter
2012-01-17 17:55 ` Eric Anholt
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=8639cnj0lh.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=eric@anholt.net \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.