Hi,
On 5/5/07, Maarten Lankhorst m.b.lankhorst@gmail.com wrote:
This avoids expensive server calls in a time critical timer.
Without priority patch it drops stddev in winmm timer tests to < 2 ms as compared to ~7 ms before. With priority patch it drops to < .20 ms.
Backwards compatibility code is kept just in case.
Even though backward compatibility is kept I worry about a couple of things. A lot of work was done on WinMM to make it portable to windows for testing and I don't like seeing new code to tie it back to unix even with the old code left in place. Also shouldn't there be a way to speed up the server performance instead? If this is accepted here then what about other areas of wine such as directx where timers similar may be used? Should we make this sort of patch global? I don't think so but then I don't know enough to no what the proper fix would be.
Thanks
Steven Edwards schreef:
Hi,
Even though backward compatibility is kept I worry about a couple of things. A lot of work was done on WinMM to make it portable to windows for testing and I don't like seeing new code to tie it back to unix even with the old code left in place. Also shouldn't there be a way to speed up the server performance instead? If this is accepted here then what about other areas of wine such as directx where timers similar may be used? Should we make this sort of patch global? I don't think so but then I don't know enough to no what the proper fix would be.
Thanks
Winmm has a generic timer interface that you could probably use in d3d as well. If windows doesn't have pipe.h and sys/pipe.h then we could change it so that this implementation is only used if sys/pipe.h or pipe.h is found. That should keep winmm portable while keeping speed on both platforms. As for making this patch global: I don't know.
Maarten
i dnt understand wot ur on abwt m8 im only 15 and plus im blonde so i hav no idea?????
From: "Steven Edwards" winehacker@gmail.com Reply-To: wine-devel@winehq.org To: wine-devel@winehq.org CC: wine-patches@winehq.org Subject: Re: winmm: Use a pipe for timer Date: Sat, 5 May 2007 16:59:26 -0400
Hi,
On 5/5/07, Maarten Lankhorst m.b.lankhorst@gmail.com wrote:
This avoids expensive server calls in a time critical timer.
Without priority patch it drops stddev in winmm timer tests to < 2 ms as compared to ~7 ms before. With priority patch it drops to < .20 ms.
Backwards compatibility code is kept just in case.
Even though backward compatibility is kept I worry about a couple of things. A lot of work was done on WinMM to make it portable to windows for testing and I don't like seeing new code to tie it back to unix even with the old code left in place. Also shouldn't there be a way to speed up the server performance instead? If this is accepted here then what about other areas of wine such as directx where timers similar may be used? Should we make this sort of patch global? I don't think so but then I don't know enough to no what the proper fix would be.
Thanks
-- Steven Edwards
"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
_________________________________________________________________ Could you be the guest MSN Movies presenter? Click Here to Audition http://www.lightscameraaudition.co.uk