From owner-freebsd-current@FreeBSD.ORG Mon Dec 27 04:25:22 2004 Return-Path: Delivered-To: freebsd-current@hub.freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id EF5DA16A4D0; Mon, 27 Dec 2004 04:25:22 +0000 (GMT) Date: Mon, 27 Dec 2004 04:25:22 +0000 From: Darren Reed To: Giorgos Keramidas Message-ID: <20041227042522.GC18879@hub.freebsd.org> References: <20041226182240.GA20920@hub.freebsd.org> <20041226205333.GA2039@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041226205333.GA2039@gothmog.gr> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Mon, 27 Dec 2004 13:07:45 +0000 cc: Scott Long cc: freebsd-current@hub.freebsd.org cc: Robert Watson Subject: Re: witness found wanting (was Re: LORs in ipfilter) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 04:25:23 -0000 On Sun, Dec 26, 2004 at 10:53:33PM +0200, Giorgos Keramidas wrote: > > Is this performance hit FreeBSD specific? I saw in ip_compat.h that on > __sgi systems mutexes are used instead of rwlocks. When I first ported IPFilter to IRIX, their equivalent of sx locks did not work in interrupt context (I think this was also true of lockmgr locks in BSD, too.) To work around this, I used mutexes instead. The #ifdef maze in 3.4's ip_compat.h is delicate so I try not to mess with it more than I have to, but later versions of IRIX do have a working lock type of this nature and I use it where available. In this case, "do not work" means "panic when attempted". Darren