From owner-freebsd-arch Fri Feb 21 22:50:48 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B99B137B401 for ; Fri, 21 Feb 2003 22:50:47 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCEF743FD7 for ; Fri, 21 Feb 2003 22:50:46 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h1M6okf98405 for ; Sat, 22 Feb 2003 01:50:46 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Sat, 22 Feb 2003 01:50:45 -0500 (EST) From: Jeff Roberson To: arch@freebsd.org Subject: More buf cache locking. Message-ID: <20030222013233.T88110-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I need to be able to pass the vnode interlock in as the lockmgr interlock in cases where we are pulling buffers off of dirty/clean lists. To support this BUF_LOCK* has to grow another argument. I am going to make a pass through the tree to add interlock where appropriate. Also, there is currently a lock for bufs on the wchan and prio fields. This is the buftimelock. This has to go away so that the vnode interlock can be used. To facilitate this I'm going to extend lockmgr to accept another pair of arguments that specify the wchan and prio. I intend to make a new function that has two extra arguments and then define an inline that supports the old semantics. If anyone objects, please let me know. Cheers, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message