Date: Wed, 1 May 2002 09:15:02 -0700 From: Alfred Perlstein <bright@mu.org> To: "Nelson, Trent ." <tnelson@switch.com> Cc: "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org> Subject: Re: Kernel spin lock facilities Message-ID: <20020501161502.GF98487@elvis.mu.org> In-Reply-To: <8F329FEDF58BD411BE5200508B10DA76056ED3A0@exchptc1.switch.com> References: <8F329FEDF58BD411BE5200508B10DA76056ED3A0@exchptc1.switch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Nelson, Trent . <tnelson@switch.com> [020501 06:41] wrote: > Hi, > > I'm working on porting the Linux Cisco VPN client kernel module to > FreeBSD. The API interface between the OS and their actual driver has four > spinlock functions that operate around a handle (void *) to a ``critical > section'': > > CNI_free_spin_lock > CNI_new_spin_lock > CNI_spin_lock > CNI_spin_unlock > > Funnily enough, these wrap the Linux spinlock_t/spin_lock*() > functionality quite nicely. Does the FreeBSD kernel offer such a trivial > spinlock facility? If not, could anyone suggest what type of locking > mechanism would best be used? man 9 mutex, see the MTX_SPIN section, but you might not need it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020501161502.GF98487>