From: Ben Pfaff Date: Tue, 5 Mar 2013 21:12:08 +0000 (-0800) Subject: timeval: Increase accuracy of cached time 4X, from 100 ms to 25 ms. X-Git-Tag: sliver-openvswitch-1.10.90-1~10^2~106 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=67a2f47310dce03f49fa4dbd9daf5b1ae93ccc20;p=sliver-openvswitch.git timeval: Increase accuracy of cached time 4X, from 100 ms to 25 ms. With CFM and other tunnel monitoring protocols, having a fairly precise time is good. My measurements don't show this change increasing CPU use. (In fact it appears to repeatably reduce CPU use slightly, from about 22% to about 20% with 1000 CFM instances, although it's not obvious why.) Bug #15171. Signed-off-by: Ben Pfaff Acked-by: Ethan Jackson --- diff --git a/lib/timeval.h b/lib/timeval.h index d5c12f065..72cf49830 100644 --- a/lib/timeval.h +++ b/lib/timeval.h @@ -43,7 +43,7 @@ BUILD_ASSERT_DECL(TYPE_IS_SIGNED(time_t)); /* Interval between updates to the reported time, in ms. This should not be * adjusted much below 10 ms or so with the current implementation, or too * much time will be wasted in signal handlers and calls to clock_gettime(). */ -#define TIME_UPDATE_INTERVAL 100 +#define TIME_UPDATE_INTERVAL 25 /* True on systems that support a monotonic clock. Compared to just getting * the value of a variable, clock_gettime() is somewhat expensive, even on