summaryrefslogtreecommitdiffstats
path: root/share/man/man9/timeout.9
Commit message (Collapse)AuthorAgeFilesLines
* add callout_schedule; besides being useful it also improvessam2008-08-021-5/+21
| | | | | | compatibility with other systems Reviewed by: ed, battlez
* - Document newly added callout_init_rw functiongabor2007-11-201-1/+26
| | | | | Requested by: attilio Reviewed by: attilio
* - Use .fn to markup untimeout in two places it was missing.jhb2005-12-011-2/+6
| | | | | | | | - Reword a confusing sentence. PR: docs/89810 Submitted by: Marius Nuennerich marius dot nuennerich at gmx dot net MFC after: 3 days
* -mdoc sweep.ru2005-11-181-1/+0
|
* Make callout_reset() return a non-zero value if a pending calloutglebius2005-09-081-5/+7
| | | | | | was rescheduled. If there was no pending callout, then return 0. Reviewed by: iedowse, cperciva
* Assorted markup fixes and minor wordsmithing.ru2005-06-151-1/+1
| | | | Approved by: re
* Add a mechanism for associating a mutex with a callout when theiedowse2005-02-071-1/+50
| | | | | | | | | | | | | | | | | | | | | | callout is first initialised, using a new function callout_init_mtx(). The callout system will acquire this mutex before calling the callout function and release it on return. In addition, the callout system uses the mutex to avoid most of the complications and race conditions inherent in asynchronous timer facilities, so mutex-protected callouts have much simpler semantics. As long as the mutex is held when invoking callout_stop() or callout_reset(), then these functions will guarantee that the callout will be stopped, even if softclock() had already begun to process the callout. Existing Giant-locked callouts will automatically pick up the new race-free semantics. This should close a number of race conditions in the USB code and probably other areas of the kernel too. There should be no change in behaviour for "MP-safe" callouts; these still need to use the techniques mentioned in timeout(9) to avoid race conditions.
* Fixed whitespace at EOL and double word.ru2005-01-281-5/+5
| | | | Uncompact enumaration to make it look better.
* Attempt to describe the race conditions that must be considerediedowse2005-01-231-9/+221
| | | | | | when using the callout subsystem. Show how the callout_pending(), callout_active() and callout_deactivate() macros can be used to achieve simpler race-free callout semantics in many situations.
* Document callout_pending() macro.glebius2004-12-291-1/+6
| | | | MFC after: 1 week
* Assorted markup, spelling, and grammar fixes.ru2004-06-161-3/+7
|
* mdoc(7) police:hmp2004-05-051-1/+2
| | | | | | * correctly place parenthisized sentences * remove hard sentence breaks * use .Vt instead of .Fn
* Introduce a callout_drain() function. This acts in the same manner ascperciva2004-04-061-11/+18
| | | | | | | | | | | callout_stop(), except that if the callout being stopped is currently in progress, it blocks attempts to reset the callout and waits until the callout is completed before it returns. This makes it possible to clean up callout-using code safely, e.g., without potentially freeing memory which is still being used by a callout. Reviewed by: mux, gallatin, rwatson, jhb
* Looks like I misread the callout code. We do not seem to hold theimp2003-10-011-11/+12
| | | | | | | | | | | | | | callout lock while the callout is happening. So the serialization that I thought was happening isn't. Therefore, remove the part of the bugs that says this. Leave in the other bug as it is very hard to work around (impossible?). Fix various typos. Also note that timeout/untimeout are considered to be the old interface and the callout interface should be used insetad. Submitted by: bde (first two) and wollman (third)
* Document the implications of the callout_stop() returning 0 if theimp2003-10-011-0/+14
| | | | | | | callout has finished or is in progress. Also document that the locking of the callout code for FreeBSD 5 has eliminated the 'or is in progress' clause as a possibility and that such elimination is an accident of the implementation and shouldn't be relied upon.
* mdoc(7) police: Use the new .In macro for #include statements.ru2001-10-011-2/+2
|
* - callout_stop() now returns an integer value instead of void sojhb2001-08-231-1/+16
| | | | | describe it. - Add a return values section.
* mdoc(7) police: s/BSD/.Bx/ where appropriate.ru2001-08-141-1/+3
|
* Removed whitespace at end-of-line; no content changes. I simply didschweikh2001-07-141-5/+5
| | | | | | | | | | cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//' BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block... Reviewed by: Silence from cvs diff -b MFC after: 7 days
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Document the mpsafe argument to callout_init().ben2001-01-311-1/+9
| | | | | | PR: 24529 Submitted by: harti brandt <brandt@fokus.gmd.de> Reviewed by: jlemon
* Prepare for mdoc(7)NG.ru2000-12-291-4/+8
|
* Use Fx macro wherever possible.ru2000-11-141-3/+13
|
* Mention more functions in the headers so whatis(1) can find them, andmarkm2000-08-161-1/+6
| | | | create links to functions so added found.
* Fixed some bugs (one serious one: timeouts were claimed to be executed atbde1999-12-271-4/+41
| | | | | | | | spl0) and some bitrot (the not-so-new callout_init/stop/reset functions were not mentioned; the callout_activate/deactivate/pending macros are still not mentioned). Submitted by: mostly by jlemon
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Fixed synopsis again. Too much was blown away by splatting a NetBSD-bde1998-01-161-4/+8
| | | | based version over the top of the FreeBSD version in rev.1.6.
* Updated timeout.9 man page describing the new callout interface. Thisgibbs1997-09-211-63/+120
| | | | man page was based on the NetBSD version.
* Fixed #include and/or prototype bugs in synopsis.bde1997-04-131-2/+2
|
* Fixed synopsis (wrong #includes and superfluous parentheses in typedef).bde1997-03-191-8/+5
| | | | | Nuked the confusing timeout_func_t typedef. It will go away in <systm.h> later.
* Revert $FreeBSD$ back to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Describe timeout() and untimeout().joerg1996-04-131-0/+92
OpenPOWER on IntegriCloud