Hi,
Yeah, I have quite a few patches that have been stuck
for a while, and many of them are also reviewed.
Just need to get around to get commit-access,
so that I don't have to bother everyone else.
I was hoping to get that done one of the coming days.
It's basically hanging on me at the moment
D
Great,
then I only can point to the 'prehash work' from Thomas Helland
'[Mesa-dev] [PATCH 0/6] Prehash all the things'
https://lists.freedesktop.org/archives/mesa-dev/2017-May/156564.html
with which I'm running during the last weeks.
No one commented other then me...
It has my 'Tested-by:' (H
Hi Dieter,
Yes, all of my GLSL compilation speedup work landed.
I'm glad glibc got a better allocator.
Marek
On Sun, Aug 6, 2017 at 7:48 PM, Dieter Nützel wrote:
> Hello Marek,
>
> with latest glibc-2.26 results on Phoronix, I remember your GREAT GLSL
> compilation speedup work. Did anything o
Hello Marek,
with latest glibc-2.26 results on Phoronix, I remember your GREAT GLSL
compilation speedup work. Did anything of this landed? --- I think not?
(Can't find related commits.)
Some other ralloc related optimizations landed during October 2016...
ralloc: don't memset ralloc_header, cl
On 7 October 2016 at 02:43, Michel Dänzer wrote:
> On 07/10/16 05:44 AM, Eric Anholt wrote:
>> Marek Olšák writes:
>>
>>> I'd like to have more feedback on the idea of using jemalloc for ralloc.
>>>
>>> Right now, I see these options:
>>>
>>> 1) Use jemalloc for ralloc and make it mandatory for a
On 07/10/16 05:44 AM, Eric Anholt wrote:
> Marek Olšák writes:
>
>> I'd like to have more feedback on the idea of using jemalloc for ralloc.
>>
>> Right now, I see these options:
>>
>> 1) Use jemalloc for ralloc and make it mandatory for all GL drivers.
>> - Distributions have shown that they are
Marek Olšák writes:
> I'd like to have more feedback on the idea of using jemalloc for ralloc.
>
> Right now, I see these options:
>
> 1) Use jemalloc for ralloc and make it mandatory for all GL drivers.
> - Distributions have shown that they are capable of doing anything
> with the Mesa source c
I'd like to have more feedback on the idea of using jemalloc for ralloc.
Right now, I see these options:
1) Use jemalloc for ralloc and make it mandatory for all GL drivers.
- Distributions have shown that they are capable of doing anything
with the Mesa source code, so they don't need --disable-
On Sun, Oct 2, 2016 at 4:03 PM, ⚛ <0xe2.0x9a.0...@gmail.com> wrote:
> Hello Marek
>
> instead of utilizing jemalloc, I strongly recommend you take a look (for
> example) at:
>
> classes such as ir_copy_propagation_elements_visitor
> file glcpp-parse.y
>
> and to put optimizations and better algorit
Hello Marek
instead of utilizing jemalloc, I strongly recommend you take a look (for
example) at:
- classes such as ir_copy_propagation_elements_visitor
- file glcpp-parse.y
and to put optimizations and better algorithms in there.
Eliminating the causes of malloc-like calls will result in
On Thu, Sep 29, 2016 at 8:19 PM, Emil Velikov wrote:
> On 29 September 2016 at 18:48, Marek Olšák wrote:
>> On Thu, Sep 29, 2016 at 4:56 PM, Emil Velikov
>> wrote:
>>> On 29 September 2016 at 11:48, Marek Olšák wrote:
On Thu, Sep 29, 2016 at 11:20 AM, Nicolai Hähnle
wrote:
> On
On 29 September 2016 at 18:48, Marek Olšák wrote:
> On Thu, Sep 29, 2016 at 4:56 PM, Emil Velikov
> wrote:
>> On 29 September 2016 at 11:48, Marek Olšák wrote:
>>> On Thu, Sep 29, 2016 at 11:20 AM, Nicolai Hähnle wrote:
On 28.09.2016 18:49, Marek Olšák wrote:
>
> From: Marek Olšák
Hi,
> The GLSL compiler can be slowed down significantly by keeping 5x
> LLVMContext in memory between compilations in radeonsi. The fact that
> radeonsi can indirectly slow down the GLSL compiler (but not LLVM) is
> a strong indication that we have a problem.
This will mean there will be two hea
On Thu, Sep 29, 2016 at 4:56 PM, Emil Velikov wrote:
> On 29 September 2016 at 11:48, Marek Olšák wrote:
>> On Thu, Sep 29, 2016 at 11:20 AM, Nicolai Hähnle wrote:
>>> On 28.09.2016 18:49, Marek Olšák wrote:
From: Marek Olšák
More info about jemalloc:
https://github.
On 29 September 2016 at 11:48, Marek Olšák wrote:
> On Thu, Sep 29, 2016 at 11:20 AM, Nicolai Hähnle wrote:
>> On 28.09.2016 18:49, Marek Olšák wrote:
>>>
>>> From: Marek Olšák
>>>
>>> More info about jemalloc:
>>>https://github.com/jemalloc/jemalloc/wiki/History
>>>
>>> Average from 3 takes
Hi Marek,
> The diff is -10.5% for a full shader-db run.
Interesting finding, did you also have a look at the memory footprint (rss)
during the shader-db Run (average and Spikes)?
Br, Clemens
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
htt
On Thu, Sep 29, 2016 at 11:20 AM, Nicolai Hähnle wrote:
> On 28.09.2016 18:49, Marek Olšák wrote:
>>
>> From: Marek Olšák
>>
>> More info about jemalloc:
>>https://github.com/jemalloc/jemalloc/wiki/History
>>
>> Average from 3 takes compiling Alien Isolation shaders from GLSL to GCN
>> byteco
On 28.09.2016 18:49, Marek Olšák wrote:
From: Marek Olšák
More info about jemalloc:
https://github.com/jemalloc/jemalloc/wiki/History
Average from 3 takes compiling Alien Isolation shaders from GLSL to GCN
bytecode:
glibc:17.183s
jemalloc: 15.558s
diff: -9.5%
The diff is -
From: Marek Olšák
More info about jemalloc:
https://github.com/jemalloc/jemalloc/wiki/History
Average from 3 takes compiling Alien Isolation shaders from GLSL to GCN
bytecode:
glibc:17.183s
jemalloc: 15.558s
diff: -9.5%
The diff is -10.5% for a full shader-db run.
---
TODO:
19 matches
Mail list logo
