Originally posted by agd5f
View Post
Announcement
Collapse
No announcement yet.
Performance Work Coming Up For Mesa 7.11
Collapse
X
-
Originally posted by hal2k1 View PostDoes the description above agree with this new article?
http://www.phoronix.com/scan.php?pag...item&px=OTAwMg
Comment
-
Originally posted by smitty3268 View PostYes, and for good reason.
This has been discussed to death over and over again. The current limiting factor in getting better OSS drivers is developer manpower, so anything that can help them out should be the #1 priority. The only people hurt by this are the devs at AMD and NVidia, and they have enough manpower to overcome the problem. Everyone else does not.
On another note (start rant, hehe):
Even though they have manpower (and that they are "huge evil corporations"TM), they usually don't have an infinite amount of money. Especially not AMD I assume...
The manpower they do have, they're probably trying to do the best they can with. Sadly that "best" usually doesn't align with what we think is the best for the Linux community. But of course I don't think the developers are to blame for this, it's usually decisions made far above their heads. They're probably just as frustrated with their managers as us other coders are, hehe
Comment
-
Originally posted by LibertyZero View PostSounds like an interesting task. What exactly has to be profiled, how is it done and is any special ability required to do that despite of a lot of patience? :-)
Comment
-
Heh... Stable ABI... "Hey Gallium dudes, forget about LLVM; stick to TGSL for ten years! Oh and Limug guys; forget about a good kernel; do it like NT!" Yeah that'll be the day, morons, when the reason for closed ddrivers is simply speed. Speed that FLOSS doesn't have because of a manpower problem and not an awesomeness problem.
Comment
-
Originally posted by V!NCENT View PostHeh... Stable ABI... "Hey Gallium dudes, forget about LLVM; stick to TGSL for ten years! Oh and Limug guys; forget about a good kernel; do it like NT!" Yeah that'll be the day, morons, when the reason for closed ddrivers is simply speed. Speed that FLOSS doesn't have because of a manpower problem and not an awesomeness problem.
Comment
-
Originally posted by smitty3268 View Post"So you're calling stupid anyone who wishes for a driver ABI."
Yes, and for good reason.
This has been discussed to death over and over again. The current limiting factor in getting better OSS drivers is developer manpower, so anything that can help them out should be the #1 priority. The only people hurt by this are the devs at AMD and NVidia, and they have enough manpower to overcome the problem. Everyone else does not.
Comment
-
Originally posted by agd5f View PostI'm not quite sure what you are asking. Radeon pageflipping support was merged for 2.6.38 and as I noted, it's vblank synced, but does reduce memory bandwidth requirements and pipeline latency since it avoids the additional blit required for the bufferswap which has a factor in performance. The frame rate if refresh rate limited, but the memory bandwidth requirements are lower. For non-vblank-synced pageflipping, the dri2 code in the xserver needs some additional work.
How does it work for non-vblank-synced?
Comment
-
Originally posted by Danny View PostIf my understanding is correct, pageflipping for vblank-synched works by changing the pointers to the back buffer during the vblank period.
How does it work for non-vblank-synced?
Comment
Comment