If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

again very useful, i have hope that using apitrace/oprofile/CS cross check i can find some bottlenecks and maybe playing a bit with tom stellard llvm compiler[won't be easy tho but should be a good way to get more intimate with gallium code ]

Comment

J?rome said, more than one year ago, that the kernel interface is quite bad and is (or will be) a bottleneck. But it's really hard to heavily modify this.

I think the kernel interface is quite good. Jerome just likes to rewrite things from scratch. It's a sport for him. Most of the kernel code is executed in another thread and runs in parallel with Mesa most of the time. You wouldn't probably even notice if the kernel code were twice as slow.

Comment

I think the kernel interface is quite good. Jerome just likes to rewrite things from scratch. It's a sport for him. Most of the kernel code is executed in another thread and runs in parallel with Mesa most of the time. You wouldn't probably even notice if the kernel code were twice as slow.

So, would it become a concern if we had open source crossfire/sli support?

Comment

I need just to wait till cards stabilize more, then he has 50? from me! However, this will happen unless Intel makes powerful GPU. In this case, it will be a hard decision!

Good work is good work. And Marek is doing it. He has 20? from me.
I have one question. Marek, after you finish r600g re-factoring what is next? Do you have the will to optimize r600g shader compiler? If yes, will you be using LLVM back-end for this endeavor?

Comment

So, would it become a concern if we had open source crossfire/sli support?

I think it's too early to talk about crossfire. We are not even on par with fglrx on single-card configurations as far as features and performance are concerned. The thing with the R300-R500 GPUs was that Catalyst 9.3 hadn't seemed to be as much optimized as it is now, so it wasn't so hard to outperform it in some tests. It's going to be much harder to compete with todays fglrx on R600 and later hardware.

Comment

OpenGL 3.1 support and bug fixes are on the top of my lists right now. OpenGL 3.1 shouldn't be so hard, because there is core Mesa support in place already.

Marek, it would be just outrageous, if you guys fix the card bottleneck. Rise the performance to at least 60% compared to catalyst, where possible before moving further. This will justify people to use and purchase AMD cards for your driver. There is little sense widening OpenGL support if barely anyone can use this fruit on AMD cards. You work will just spread out to other chips, that have already that bottlenecking solved. Please!

Comment

Marek, it would be just outrageous, if you guys fix the card bottleneck. Rise the performance to at least 60% compared to catalyst, where possible before moving further. This will justify people to use and purchase AMD cards for your driver. There is little sense widening OpenGL support if barely anyone can use this fruit on AMD cards. You work will just spread out to other chips, that have already that bottlenecking solved. Please!

Second that. Most games run with this level of OpenGL support, but too slow. Especially on the APU front.