From owner-cvs-src@FreeBSD.ORG Tue Jun 20 22:44:23 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16D1216A47A; Tue, 20 Jun 2006 22:44:23 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F2EF43D58; Tue, 20 Jun 2006 22:44:20 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.3) with ESMTP id k5KMiJ9J094220; Wed, 21 Jun 2006 02:44:19 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Wed, 21 Jun 2006 02:44:19 +0400 (MSD) From: Maxim Konovalov To: Scott Long In-Reply-To: <449874B5.50909@samsco.org> Message-ID: <20060621024346.E90615@mp2.macomnet.net> References: <200606202141.k5KLfETG075895@repoman.freebsd.org> <20060621014634.U55744@mp2.macomnet.net> <44987135.1070007@samsco.org> <20060621020909.N56083@mp2.macomnet.net> <449874B5.50909@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man9 lock.9 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 22:44:23 -0000 [...] > > > >Btw, as I see there are not many consumers of lock.9 > > > >infrastructure comparing to mutex.9, sx.9 etc in our tree. Is > > > >it something derecated? > > > > > > > > > >I guess that VFS doesn't count as being important? > > > > > > As an average user I just want to know what pros and contras for > > using lock.9 vs all other locking primitivies. It is not clear > > from our man pages and arch book. Sorry if I'm asking something > > completely stupid. > > > > lockmgr is somewhat analogous to an SX lock. However, due to some > of the special considerations needed by VFS in terms of the vnode > life cycle and blocking for I/O, they aren't completely functionally > equivalent to an SX lock. It would be nice to fix VFS to not need > these special considerations, but that is a very complicated and > risky task. Thanks! -- Maxim Konovalov