From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 23 02:22:14 2007 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E19E616A404 for ; Fri, 23 Mar 2007 02:22:14 +0000 (UTC) (envelope-from xpeng@buffalo.edu) Received: from front2.acsu.buffalo.edu (warmfront.acsu.buffalo.edu [128.205.6.88]) by mx1.freebsd.org (Postfix) with SMTP id AD88A13C46C for ; Fri, 23 Mar 2007 02:22:12 +0000 (UTC) (envelope-from xpeng@buffalo.edu) Received: (qmail 5583 invoked from network); 23 Mar 2007 01:55:30 -0000 Received: from mailscan6.acsu.buffalo.edu (128.205.7.95) by front2.acsu.buffalo.edu with SMTP; 23 Mar 2007 01:55:30 -0000 Received: (qmail 19947 invoked by uid 60001); 23 Mar 2007 01:55:30 -0000 To: hackers@FreeBSD.org Date: Thu, 22 Mar 2007 21:55:30 -0400 From: xpeng@buffalo.edu Message-ID: <1174614930.4603339242c9a@mail2.buffalo.edu> References: <000c01c76cbc$7ba87ec0$72f97c40$@pl> In-Reply-To: <000c01c76cbc$7ba87ec0$72f97c40$@pl> X-Mailer: University at Buffalo WebMail Cyrusoft SilkyMail v1.1.11 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Originating-IP: 128.205.234.145 X-UB-Relay: (internal) X-PM-EL-Spam-Prob: : 7% Cc: Subject: mtx_unlock in kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2007 02:22:15 -0000 If I want to use mtx_unlock for some threads, should I use mtx_lock() before?