From owner-freebsd-arch Sun Feb 23 19:52: 6 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 AE9E337B401 for ; Sun, 23 Feb 2003 19:52:05 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C65943FD7 for ; Sun, 23 Feb 2003 19:52:05 -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 h1O3q3M21887; Sun, 23 Feb 2003 22:52:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Sun, 23 Feb 2003 22:52:02 -0500 (EST) From: Jeff Roberson To: Kirk McKusick Cc: arch@FreeBSD.ORG Subject: Re: More buf cache locking. (patch) In-Reply-To: <200302240252.h1O2qpFL066069@beastie.mckusick.com> Message-ID: <20030223224757.R19976-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 On Sun, 23 Feb 2003, Kirk McKusick wrote: > I forgot, the patch is at: > > http://www.chesapeake.net/~jroberson/bcache.diff > > These changes look reasonable to me. > Thanks, I'm really glad you looked that over. I will have some changes to the softdep code for you to review soon. It needs to acquire the vnode interlock to protect the dirty and clean queues. The interlock is required since io can complete while the vnode lock is not held and these lists are modified at interrupt time. I intend to add an interlock argument to getdirtybuf(). Also, what are your thoughts on how smp safe ufs/ffs is? Are there any internal datastructures that need locking? If vnodes and mounts were locked along with the buf cache and name cache do you think it would be safe to drop Giant? We're very close to this point now. Thanks, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message