I've looked into Mesa hash-table some time ago, didn't finish anything
(sigh, I have troubles finishing things off :( ). Anyway some things I
got from there, in no particular order:
1. I've created a tool that records hash query traces and then replays
them, sorta like apitrace for hashing. We
On Wed, 2017-02-08 at 21:35 +0100, Thomas Helland wrote:
> I was cleaning up my local git repo, and came across this series.
> Last time it was discussed was all the way back in April 2015.
> Things looked pretty good back then, but we where seeing a smaller
> regression in CPU-bound scenarios as E
On Wed, 2017-02-08 at 15:59 -0800, Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 3:01 PM, Marek Olšák wrote:
> > I think this is good stuff. I'd gladly take it just for the shader-
> > db
> > improvement.
> >
>
> Agreed. If it really did hurt minecraft before, we should try that
> again just t
On 09/02/17 18:31, Thomas Helland wrote:
2017-02-09 1:57 GMT+01:00 Timothy Arceri :
On Wed, 2017-02-08 at 21:35 +0100, Thomas Helland wrote:
I was cleaning up my local git repo, and came across this series.
Last time it was discussed was all the way back in April 2015.
Things looked pretty go
On 09/02/17 18:31, Thomas Helland wrote:
2017-02-09 1:57 GMT+01:00 Timothy Arceri :
On Wed, 2017-02-08 at 21:35 +0100, Thomas Helland wrote:
I was cleaning up my local git repo, and came across this series.
Last time it was discussed was all the way back in April 2015.
Things looked pretty go
2017-02-09 1:57 GMT+01:00 Timothy Arceri :
> On Wed, 2017-02-08 at 21:35 +0100, Thomas Helland wrote:
>> I was cleaning up my local git repo, and came across this series.
>> Last time it was discussed was all the way back in April 2015.
>> Things looked pretty good back then, but we where seeing a
On Wed, 8 Feb 2017 15:59:55 -0800
Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 3:01 PM, Marek Olšák wrote:
>
> > I think this is good stuff. I'd gladly take it just for the
> > shader-db improvement.
> >
>
> Agreed. If it really did hurt minecraft before, we should try that
> again just t
On Wed, 8 Feb 2017 21:35:36 +0100
Thomas Helland wrote:
> I was cleaning up my local git repo, and came across this series.
> Last time it was discussed was all the way back in April 2015.
> Things looked pretty good back then, but we where seeing a smaller
> regression in CPU-bound scenarios as
On Wed, Feb 8, 2017 at 3:01 PM, Marek Olšák wrote:
> I think this is good stuff. I'd gladly take it just for the shader-db
> improvement.
>
Agreed. If it really did hurt minecraft before, we should try that again
just to be sure, but I like faster shader compilation.
> Marek
>
> On Wed, Feb 8
I think this is good stuff. I'd gladly take it just for the shader-db
improvement.
Marek
On Wed, Feb 8, 2017 at 11:35 PM, Thomas Helland
wrote:
> 2017-02-08 22:07 GMT+01:00 Thomas Helland :
>> 2017-02-08 21:35 GMT+01:00 Thomas Helland :
>>> I was cleaning up my local git repo, and came across th
2017-02-08 22:07 GMT+01:00 Thomas Helland :
> 2017-02-08 21:35 GMT+01:00 Thomas Helland :
>> I was cleaning up my local git repo, and came across this series.
>> Last time it was discussed was all the way back in April 2015.
>> Things looked pretty good back then, but we where seeing a smaller
>> r
2017-02-08 21:35 GMT+01:00 Thomas Helland :
> I was cleaning up my local git repo, and came across this series.
> Last time it was discussed was all the way back in April 2015.
> Things looked pretty good back then, but we where seeing a smaller
> regression in CPU-bound scenarios as Eric found wit
I was cleaning up my local git repo, and came across this series.
Last time it was discussed was all the way back in April 2015.
Things looked pretty good back then, but we where seeing a smaller
regression in CPU-bound scenarios as Eric found with forcing software
rendering while running Minecraf
13 matches
Mail list logo
