Messages in this thread | | | Date | Mon, 10 Jun 2013 16:12:09 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: [PATCH] kernel: timer: looping issue, need reset variable 'found' |
| |
On Sun, 9 Jun 2013, Chen Gang wrote:
> > According to __internal_add_timer(), in _next_timer_interrupt(), when > 'tv1.vec' find one, but need 'cascade bucket(s)', we still need find > each slot of 'tv*.vec'.
No, we do not. We only need to scan the first cascade array after the enqueued timer. If there is nothing in tv2 which might come before the found timer, then any timer in tv3 will be later than the one we found in the primary wheel.
> So need reset variable 'found', so can fully scan ''do {...} while()'' > for 'tv*.vec'.
And thereby lose the information, that we already found a timer in the scan of the primary array.
Thanks,
tglx
| |