Date: Fri, 26 May 2000 10:38:05 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Chuck Paterson <cp@bsdi.com>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Terry Lambert <tlambert@primenet.com>, arch@FreeBSD.ORG Subject: Re: Preemptive kernel on older X86 hardware Message-ID: <200005261738.KAA90605@apollo.backplane.com> References: <200005251700.LAA25373@berserker.bsdi.com> <392E97B7.1A575FAC@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> Almost.) I certainly think that the actually locking
:> stuff can be in a function but we really want to wrap the
:> function in a macro so we can put tracing in. Being able
:> to look at a trace and see file and line numbers for mutex
:> locks and unlocks is invaluable.
:
:Won't declaring the function as inline work?
:
:--
:Daniel C. Sobral (8-DCS)
Not if you want to use __FILE__, __LINE__, etc... for tracing purposes.
Besides, using an inline there creates a lot of bloat.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005261738.KAA90605>