| timeout.9 (128951) | timeout.9 (130582) |
|---|---|
| 1.\" $NetBSD: timeout.9,v 1.2 1996/06/23 22:32:34 pk Exp $ 2.\" 3.\" Copyright (c) 1996 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Paul Kranenburg. 8.\" --- 20 unchanged lines hidden (view full) --- 29.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" | 1.\" $NetBSD: timeout.9,v 1.2 1996/06/23 22:32:34 pk Exp $ 2.\" 3.\" Copyright (c) 1996 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Paul Kranenburg. 8.\" --- 20 unchanged lines hidden (view full) --- 29.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" |
| 37.\" $FreeBSD: head/share/man/man9/timeout.9 128951 2004-05-05 10:47:19Z hmp $ | 37.\" $FreeBSD: head/share/man/man9/timeout.9 130582 2004-06-16 08:33:57Z ru $ |
| 38.\" 39.Dd September 10, 1996 40.Dt TIMEOUT 9 41.Os 42.Sh NAME 43.Nm timeout , 44.Nm untimeout , 45.Nm callout_handle_init , --- 52 unchanged lines hidden (view full) --- 98.Fn timeout 99is a 100.Ft struct callout_handle 101which can be used in conjunction with the 102.Fn untimeout 103function to request that a scheduled timeout be canceled. 104The 105.Fn timeout | 38.\" 39.Dd September 10, 1996 40.Dt TIMEOUT 9 41.Os 42.Sh NAME 43.Nm timeout , 44.Nm untimeout , 45.Nm callout_handle_init , --- 52 unchanged lines hidden (view full) --- 98.Fn timeout 99is a 100.Ft struct callout_handle 101which can be used in conjunction with the 102.Fn untimeout 103function to request that a scheduled timeout be canceled. 104The 105.Fn timeout |
| 106call is the old style and new code should use the callout_* functions. | 106call is the old style and new code should use the 107.Fn callout_* 108functions. |
| 107.Pp 108The function 109.Fn callout_handle_init 110can be used to initialize a handle to a state which will cause 111any calls to untimeout with that handle to return with no side 112effects. 113.Pp 114Assigning a callout handle the value of --- 24 unchanged lines hidden (view full) --- 139or assigned the value of 140.Fn CALLOUT_HANDLE_INITIALIZER "&handle" 141before being passed to 142.Fn untimeout . 143The behavior of calling untimeout without a previously initialized handle 144is undefined. 145The 146.Fn untimeout | 109.Pp 110The function 111.Fn callout_handle_init 112can be used to initialize a handle to a state which will cause 113any calls to untimeout with that handle to return with no side 114effects. 115.Pp 116Assigning a callout handle the value of --- 24 unchanged lines hidden (view full) --- 141or assigned the value of 142.Fn CALLOUT_HANDLE_INITIALIZER "&handle" 143before being passed to 144.Fn untimeout . 145The behavior of calling untimeout without a previously initialized handle 146is undefined. 147The 148.Fn untimeout |
| 147call is the old style and new code should use the callout_* functions. | 149call is the old style and new code should use the 150.Fn callout_* 151functions. |
| 148.Pp 149As handles are recycled by the system, it is possible (although unlikely) 150that a handle from one invocation of 151.Fn timeout 152may match the handle of another invocation of 153.Fn timeout 154if both calls used the same function pointer and argument, and the first 155timeout is expired or canceled before the second call. --- 15 unchanged lines hidden (view full) --- 171.Fn callout_reset 172are low-level routines for clients who wish to allocate their own 173callout structures. 174.Pp 175The function 176.Fn callout_init 177initializes a callout so it can be passed to 178.Fn callout_stop , | 152.Pp 153As handles are recycled by the system, it is possible (although unlikely) 154that a handle from one invocation of 155.Fn timeout 156may match the handle of another invocation of 157.Fn timeout 158if both calls used the same function pointer and argument, and the first 159timeout is expired or canceled before the second call. --- 15 unchanged lines hidden (view full) --- 175.Fn callout_reset 176are low-level routines for clients who wish to allocate their own 177callout structures. 178.Pp 179The function 180.Fn callout_init 181initializes a callout so it can be passed to 182.Fn callout_stop , |
| 179.Fn callout_drain | 183.Fn callout_drain |
| 180or 181.Fn callout_reset 182without any side effects. 183If the 184.Fa mpsafe 185argument is zero, 186the callout structure is not considered to be 187.Dq multi-processor safe ; --- 67 unchanged lines hidden --- | 184or 185.Fn callout_reset 186without any side effects. 187If the 188.Fa mpsafe 189argument is zero, 190the callout structure is not considered to be 191.Dq multi-processor safe ; --- 67 unchanged lines hidden --- |