11-29-2010, 03:13 PM
Just that with current design for r600g i don't think we can't match 50% of fglrx speed on things like nexuiz or newer game/engine. So you won't see any major boost until a complete rewrite (shader compiler excluded). That's my current feeling, i could be wrong.
Originally Posted by pingufunkybeat
11-29-2010, 04:02 PM
Is the r600g design considerably different from r300g (of course, the hardware architectures are very different)?
I believe that r300g passed the 50% mark.
Also, do you think that a complete rewrite is feasible/planned? Being stuck at <50% of the maximum forever would be a bit disappointing.
11-29-2010, 04:31 PM
It's not even finished yet and it requires a rewrite already?
Originally Posted by glisse
That is more than disappointing...
11-29-2010, 05:17 PM
That's not disappointing, that's expected and encouraging. There's only one kind of software that doesn't get constantly rewritten: dead software.
Originally Posted by HokTar
As the drivers gain more features (and hence more real-world testing), bottlenecks will appear and/or shift around. And as the developers gain more experience, existing architectural deficiencies will be discovered and dealt with.
(Note that a rewrite doesn't mean "throw away everything and start from scratch". It means things like, "hey, if we move state validation from part X to part Y, we can avoid re-validations under circumstances Z and W and increase batch submission performance by up to 15%.")
11-29-2010, 05:20 PM
Well, glisse wrote: "until a complete rewrite (shader compiler excluded)".
Originally Posted by BlackStar
That pretty much sounds like we have to restart from (almost) scratch. Obviously, I hope what you said is correct but it does not seem so.
11-29-2010, 05:34 PM
I suspect glisse is talking about more than just the actual r600g driver... usually you find bottlenecks scattered all through the stack.
I don't think he is saying "just rewrite the r600g part and everything will be fine"... remember that the r600g code is only 1-2% of the 3D driver stack, and AFAIK this is the first time the open source stack has really been put to work on high performance graphics hardware.
Things that were "nicely tuned" in the r200 days can easily become major bottlenecks on newer graphics hardware simply because the newer GPUs are so much faster.
11-29-2010, 05:46 PM
Anyway, I just hope that the rate of improvements will not slow down.
Btw, for the last few days there are barely any commits to mesa master. Is there a specific reason for that?
11-29-2010, 08:13 PM
Probably the US holiday.
Originally Posted by HokTar
11-30-2010, 04:30 AM
11-30-2010, 08:56 AM
I never asked but why in the world users are running away from AMD closed driver to open source, when AMD DOES support the closed driver for linux on their latest cards?
Why there are tons of issues and so many bugs that people are relieved to have the open source? How many AMD engineers are assigned for the AMD closed driver?
Tags for this Thread