Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | when panicing from timeout_add being < 0, print the value; ok miod | 2004-12-28 | 1 | -2/+2 | |
| | |||||
* | simplify slightly, kill lvalue weirdness that's not ANSI C. | 2004-12-12 | 1 | -8/+9 | |
| | | | | okay nordin@ | ||||
* | Diff from art@: | 2004-11-10 | 1 | -2/+9 | |
| | | | | | | | | | Update ticks in timeout_hardclock_update to avoid errors in hardclock (this is the third time we mess up here). ticks is only used for timeouts anyway. At the same protect updating ticks with timeout_mutex and be slightly more paranoid in timeout_hardclock_update. ok tdeval@ miod@ | ||||
* | The timeout wheels are manipulated by hardclock that's not protected with | 2004-07-20 | 1 | -30/+19 | |
| | | | | biglock. We need to protect them with a mutex. | ||||
* | Two term license with approval from nordin@ | 2003-06-03 | 1 | -5/+2 | |
| | |||||
* | Typos; from Julien Bordet <zejames@greyhats.org> | 2003-05-17 | 1 | -2/+2 | |
| | | | | Close PR 3262 | ||||
* | diff from nordin@ to prevent wraparound on long uptime machines. | 2003-04-13 | 1 | -2/+2 | |
| | | | | ok art@ deraadt@ miod@ tdeval@ | ||||
* | - Lock the timeout wheel after the diagnostic checks. | 2002-12-08 | 1 | -3/+4 | |
| | | | | - show timeout_todo in the ddb command. | ||||
* | First round of __P removal in sys | 2002-03-14 | 1 | -2/+2 | |
| | |||||
* | Make rescheduling to a later time faster. ok art@ | 2002-02-15 | 1 | -8/+18 | |
| | |||||
* | New scalable implementation with constant time add and delete. ok deraadt@ | 2001-12-22 | 1 | -122/+151 | |
| | |||||
* | Rename timeout_init to timeout_startup to deconfuse a bit. | 2001-09-12 | 1 | -2/+2 | |
| | |||||
* | Remove even more leftovers from old timeouts. | 2001-08-23 | 1 | -9/+1 | |
| | |||||
* | Remove the old timeout legacy code. | 2001-08-23 | 1 | -64/+1 | |
| | |||||
* | Add some DIAGNOSTIC checks that panic on some of the common mistakes. | 2001-03-28 | 1 | -7/+31 | |
| | |||||
* | Triggered mechanism allows a handler to figure out whether a given | 2001-03-15 | 1 | -1/+4 | |
| | | | | timeout is actually executing. | ||||
* | typo (incidentally, removed a bogus -k in the cvs file, the update | 2001-02-16 | 1 | -2/+2 | |
| | | | | will trigger $OpenBSD$ fill-in) | ||||
* | timeout_add: Remove the right timeout when we see that it is on the list. | 2000-06-20 | 1 | -2/+2 | |
| | |||||
* | from art@: | 2000-05-08 | 1 | -2/+9 | |
| | | | | | | | in timeout_hardclock_update() check out if there is anything in the timeout queue before calculating the return value. thanks to Adam Rogoyski <rogoyski@cs.utexas.edu> for debugging and testing help. | ||||
* | Provide methods to check if a timeout was initalized and if it is scheduled. | 2000-03-23 | 1 | -3/+3 | |
| | |||||
* | Preserve the FIFO order of issued timeouts. | 2000-03-23 | 1 | -2/+2 | |
| | |||||
* | New API for timeouts. Replaces the old timeout()/untimeout() API and | 2000-03-23 | 1 | -0/+300 | |
makes it the callers responsibility to allocate resources for the timeouts. This is a KISS implementation and does _not_ solve the problems of slow handling of a large number of pending timeouts (this will be solved in future work) (although hardclock is now guarateed to take constant time for handling of timeouts). Old timeout() and untimeout() are implemented as wrappers around the new API and kept for compatibility. They will be removed as soon as all subsystems are converted to use the new API. |