On 11 June 2010 16:02, Steven McCoy <[email protected]> wrote: > I've only seen the worst case scenario, like the 16ms timing in Windows, > nothing much about Nehalem or event the Red Hat vsyscall other than they are > "better". > > The Red Hat detail,
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.0/html/Realtime_Tuning_Guide/sect-Realtime_Tuning_Guide-Realtime_Specific_Tuning-RT_Specific_gettimeofday_speedup.html This older article on Oracle seems more informative, http://kevinclosson.wordpress.com/2007/01/24/gettimeofday-and-oracle-on-amd-processors/ "It takes 324 cycles per call to complete 1 million GTOD calls without RDTSCP and 221 cycles per call with the capability." Referencing this article, http://developer.amd.com/documentation/articles/Pages/1214200692.aspx <http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.0/html/Realtime_Tuning_Guide/sect-Realtime_Tuning_Guide-Realtime_Specific_Tuning-RT_Specific_gettimeofday_speedup.html> -- Steve-o
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
