mirror of
https://github.com/openvswitch/ovs
synced 2025-10-19 14:37:21 +00:00
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 <blp@nicira.com> Acked-by: Ethan Jackson <ethan@nicira.com>
This commit is contained in:
@@ -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
|
||||
|
Reference in New Issue
Block a user