vppinfra: remove time jump workaround
A partial revert of gerrit 25729. The last_run_time == 0.0 check is
necessary and remains in place.
Type: fix
Fixes: 3d9f134
Signed-off-by: Dave Barach <dave@barachs.net>
Change-Id: I3d2c9f90b2bc867f02c4749a5b19f997b84185b9
This commit is contained in:
@ -533,20 +533,6 @@ static inline
|
||||
return callback_vector_arg;
|
||||
}
|
||||
|
||||
/*
|
||||
* Refuse to do anything if we're about to process way too many slots.
|
||||
* Should never come anywhere close to happening, with the possible exception
|
||||
* of cases involving a large forward jump in the timebase.
|
||||
*/
|
||||
if (nticks > (1 << (TW_RING_SHIFT + 1)))
|
||||
{
|
||||
if (nticks / tw->ticks_per_second > 100e-3)
|
||||
clib_warning ("Excessive nticks %u at %.6f last run %.6f",
|
||||
nticks, now, tw->last_run_time);
|
||||
tw->last_run_time = now;
|
||||
return callback_vector_arg;
|
||||
}
|
||||
|
||||
if (callback_vector_arg == 0)
|
||||
{
|
||||
_vec_len (tw->expired_timer_handles) = 0;
|
||||
|
Reference in New Issue
Block a user