Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Sep 2011 09:17:41 +0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Riccardo Cattaneo <cattaneo.riccardo@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Kernel timers infrastructure
Message-ID:  <CAJ-VmomY7bnzUNoGarHhRPi52-Qbc9CXbmj2%2ByF2O6y5Wau=FQ@mail.gmail.com>
In-Reply-To: <2778D90F-F718-446E-8ABB-627790F00A93@gmail.com>
References:  <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> <CAJ-VmonnTuFyQgBWQRByfhZr=quD0mfmxPc=UFUHTAdBHt%2BJ0g@mail.gmail.com> <2778D90F-F718-446E-8ABB-627790F00A93@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11 September 2011 09:02, Riccardo Cattaneo
<cattaneo.riccardo@gmail.com> wrote:
> Of course, the module from which I'm calling them must be already loaded and initialized, isn't it?
> Riccardo

Well, yes - but then, you can just add something to the module load
code to start off the callout.

There are race conditions to keep in mind though - the callout may
just about to be in-play when you go to remove it. The callout manpage
points out these situations under "Avoiding Race Conditions."


Adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomY7bnzUNoGarHhRPi52-Qbc9CXbmj2%2ByF2O6y5Wau=FQ>