From: Daniel Vetter <daniel@ffwll.ch>
To: Matt Turner <mattst88@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Make sample_c messages go faster on Haswell.
Date: Tue, 11 Nov 2014 11:16:49 +0100 [thread overview]
Message-ID: <20141111101649.GI25711@phenom.ffwll.local> (raw)
In-Reply-To: <CAEdQ38E_wZP5QUUTNyDw3NwiV5Ld7e5rS7xk2fha7R6qB7Z0=w@mail.gmail.com>
On Fri, Nov 07, 2014 at 10:46:31AM -0800, Matt Turner wrote:
> On Wed, Oct 29, 2014 at 2:12 PM, Kenneth Graunke <kenneth@whitecape.org> wrote:
> > Haswell significantly improved the performance of sampler_c messages,
> > but the optimization appears to be off by default. Later platforms
> > remove this bit, and apparently always enable the optimization.
> >
> > Improves performance in "Counter Strike: Global Offensive" by 18%
> > at default settings on Iris Pro. No Piglit regressions.
>
> Discussion seems to have ended, but Mesa really needs this.
>
> So, Kernel Team, how are we going to make sure Mesa gets this 18%
> performance improvement?
Someone writes the patches+tests and everything, gets it all reviewed and
I'll merge it.
I'd prefer if we could do this with the cmd parser, but that thing seems
to be eternally stuck. So a new execbuf flag is imo ok too. execbuf
already tracks a few other lonesome bits and makes sure userspace actually
gets the setting it requests, so should work out.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-11 10:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 22:12 [PATCH] drm/i915: Make sample_c messages go faster on Haswell Kenneth Graunke
2014-10-30 8:50 ` Ville Syrjälä
2014-10-30 9:00 ` Ville Syrjälä
2014-10-30 9:32 ` Kenneth Graunke
2014-10-30 11:01 ` Ville Syrjälä
2014-10-30 17:32 ` Kenneth Graunke
2014-10-30 19:26 ` Ville Syrjälä
2014-10-30 19:57 ` Kenneth Graunke
2014-10-31 9:27 ` Ville Syrjälä
2014-10-31 9:43 ` Jani Nikula
2014-11-03 12:48 ` Daniel Vetter
[not found] ` <CAKMK7uH7-ar7OB2sdZ0phoZJ6j8-660Nr_c5CyiZRqTfgtMGHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-04 8:48 ` [Intel-gfx] " Xiang, Haihao
2014-11-03 16:15 ` Dave Gordon
2014-11-07 18:46 ` Matt Turner
2014-11-11 10:16 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-01 0:23 Kenneth Graunke
2015-01-05 0:48 ` shuang.he
2015-01-05 13:19 ` Daniel Vetter
2015-01-05 21:39 ` Kenneth Graunke
2015-01-06 5:11 ` Xiang, Haihao
2015-01-06 5:54 ` Kenneth Graunke
2015-01-06 6:39 ` Xiang, Haihao
2015-01-06 7:03 ` Kenneth Graunke
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=20141111101649.GI25711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mattst88@gmail.com \
/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