From owner-p4-projects@FreeBSD.ORG Thu Nov 6 10:30:45 2003 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 8B1AF16A4D0; Thu, 6 Nov 2003 10:30:45 -0800 (PST) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D9DE16A4CE; Thu, 6 Nov 2003 10:30:45 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CBED43FE9; Thu, 6 Nov 2003 10:30:44 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hA6IUe0x091734 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 6 Nov 2003 10:30:41 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: "M. Warner Losh" , sam@freebsd.org Date: Thu, 6 Nov 2003 10:32:37 -0800 User-Agent: KMail/1.5.3 References: <200311060513.hA65Da5J091575@repoman.freebsd.org> <20031106.012601.39876884.imp@bsdimp.com> In-Reply-To: <20031106.012601.39876884.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311061032.37691.sam@errno.com> cc: perforce@freebsd.org Subject: Re: PERFORCE change 41566 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 18:30:46 -0000 On Thursday 06 November 2003 12:26 am, M. Warner Losh wrote: > In message: <200311060513.hA65Da5J091575@repoman.freebsd.org> > > Sam Leffler writes: > : diff reduction against head > : - SIS_UNLOCK(sc); > : (*ifp->if_input)(ifp, m); > : - SIS_LOCK(sc); > > does this mean that we can call if_input with our locks held? sis's lock is setup MTX_RECURSE in which case re-entry is handled. You only need to release the lock when you may be re-entered and it's not setup as recursive. I think recursive locks are bad but so long as the driver is setup to use them I'm not releasing them when calling up. Sam