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 :cool:]
Printable View
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.
A great think to help Marek is to buy him a beer or two. In his account you have his paypal address.
Marek, you already have my 20€ of thanks.
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.
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!
If you have the latest Mesa and DDX, try to enable 2D tiling in xorg.conf. It should give you a nice boost in bandwidth-limited apps.