diff options
| author | paul <paul> | 2005-11-14 12:07:47 +0000 |
|---|---|---|
| committer | paul <paul> | 2005-11-14 12:07:47 +0000 |
| commit | 190880dc790007a14911ef8c170af33a50a7a674 (patch) | |
| tree | 8de89e02883f522cd5d730a416ce771fd2f23ed2 /lib/ChangeLog | |
| parent | 31a5976bb99f1875ebcfc29a6359f3a7ae81a795 (diff) | |
2005-11-14 Paul Jakma <paul.jakma@sun.com>
* (general) Add state to detect queue floods. There's no sense
trying to be sparing of CPU resources, if the queue is
flooding and using ever more memory resources. we should just
get on with clearing the queue.
The sense of delay and hold were wrong way around, fix.
* workqueue.h: (struct work_queue) Add status bitfield. Add
'flood' integer to workqueue spec. Add runs_since_clear
counter to workqueue.
* workqueue.c: (work_queue_new) set defaults for delay, hold
and flood.
(work_queue_add) initial schedule should use delay, not hold.
(show_work_queues) Print flood field, conserve whitespace.
(work_queue_unplug) use delay, not hold.
(work_queue_run) consecutive runs should be seperated by hold
time, not delay.
Keep track of number of consecutive runs, go into 'overdrive'
if queue is being flooded, we can't avoid making heavy use of
resources, better to use CPU than ever more RAM.
Diffstat (limited to 'lib/ChangeLog')
| -rw-r--r-- | lib/ChangeLog | 23 |
1 files changed, 22 insertions, 1 deletions
diff --git a/lib/ChangeLog b/lib/ChangeLog index 106de477..b6407c4a 100644 --- a/lib/ChangeLog +++ b/lib/ChangeLog @@ -1,4 +1,25 @@ -2005-11-12 Paul Jakma <paul.jakma@sun.com> +2005-11-14 Paul Jakma <paul.jakma@sun.com> + + * (general) Add state to detect queue floods. There's no sense + trying to be sparing of CPU resources, if the queue is + flooding and using ever more memory resources. we should just + get on with clearing the queue. + The sense of delay and hold were wrong way around, fix. + * workqueue.h: (struct work_queue) Add status bitfield. Add + 'flood' integer to workqueue spec. Add runs_since_clear + counter to workqueue. + * workqueue.c: (work_queue_new) set defaults for delay, hold + and flood. + (work_queue_add) initial schedule should use delay, not hold. + (show_work_queues) Print flood field, conserve whitespace. + (work_queue_unplug) use delay, not hold. + (work_queue_run) consecutive runs should be seperated by hold + time, not delay. + Keep track of number of consecutive runs, go into 'overdrive' + if queue is being flooded, we can't avoid making heavy use of + resources, better to use CPU than ever more RAM. + +2005-11-05 Paul Jakma <paul.jakma@sun.com> * routemap.c: (vty_show_route_map_entry) call action is seperate from exit action, latter should still be printed |