K 10
svn:author
V 5
kmacy
K 8
svn:date
V 27
2009-05-18T19:01:32.505742Z
K 7
svn:log
V 1002
180608:
Fix a race which could result in some timeout buckets being skipped.
 - When a tick occurs on a cpu, iterate from cs_softticks until ticks.
   The per-cpu tick processing happens asynchronously with the actual
   adjustment of the 'ticks' variable.  Sometimes the results may
   be visible before the local call and sometimes after.  Previously this
   could cause a one tick window where we didn't evaluate the bucket.
 - In softclock fetch curticks before incrementing cc_softticks so we
   don't skip insertions which were made for the current time.

Sponsored by:	Nokia

181191
add callout_schedule; besides being useful it also improves
compatibility with other systems

Reviewed by:	ed, battlez

184385
After a machine has been up for a bit more than 20 days with HZ=1000,
"ticks" goes negative.  This breaks the signed comparison in softclock.
This causes sleep() to never wake up, tcp to stop, etc etc.  This is
bad(TM).  Use the SEQ_LT() method from tcp's sequence number comparisons.

END