Date: Thu, 2 Oct 2014 20:59:33 GMT From: John Baldwin <jhb@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 1201064 for review Message-ID: <201410022059.s92KxX7a070145@skunkworks.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@1201064?ac=10 Change 1201064 by jhb@jhb_jhbbsd on 2014/10/02 20:58:49 More fixes. Submitted by: wblock Affected files ... .. //depot/projects/smpng/share/man/man9/timeout.9#17 edit Differences ... ==== //depot/projects/smpng/share/man/man9/timeout.9#17 (text+ko) ==== @@ -463,10 +463,10 @@ the callout by another thread. In particular, since callout functions typically acquire a lock as their first action, the callout function may have already been invoked, -but be blocked waiting for that lock at the time that another thread +but is blocked waiting for that lock at the time that another thread tries to reset or stop the callout. .Pp -One of the following approaches can be used to address these +There are three main techniques for addressing these synchronization concerns. The first approach is preferred as it is the simplest: .Bl -enum -offset indent
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201410022059.s92KxX7a070145>