Date: Fri, 3 Oct 2014 19:34:22 GMT From: John Baldwin <jhb@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 1201096 for review Message-ID: <201410031934.s93JYM3a030962@skunkworks.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@1201096?ac=10 Change 1201096 by jhb@jhb_ralph on 2014/10/03 19:33:34 More fixes. Submitted by: wblock Affected files ... .. //depot/projects/smpng/share/man/man9/timeout.9#18 edit Differences ... ==== //depot/projects/smpng/share/man/man9/timeout.9#18 (text+ko) ==== @@ -178,7 +178,8 @@ callout function and releases it after the function returns. If the callout was cancelled while the callout subsystem waited for the associated lock, -the callout function is not called and the associated lock is released. +the callout function is not called, +and the associated lock is released. This guarantees that stopping or rescheduling the callout will not race with the callout function itself because the associated lock must be held to stop or reschedule the callout. @@ -401,13 +402,13 @@ and .Fn callout_schedule functions schedule the callout to execute in the softclock thread of the CPU -it is currently assigned to. +to which it is currently assigned. .Pp -The softclock threads are not pinned to their respective CPUs by default. +Softclock threads are not pinned to their respective CPUs by default. The softclock thread for CPU 0 can be pinned to CPU 0 by setting the .Va kern.pin_default_swi loader tunable to a non-zero value. -The softclock threads for CPUs other than zero can be pinned to their +Softclock threads for CPUs other than zero can be pinned to their respective CPUs by setting the .Va kern.pin_pcpu_swi loader tunable to a non-zero value.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201410031934.s93JYM3a030962>