From owner-freebsd-hackers  Tue Aug 17 14:12:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17])
	by hub.freebsd.org (Postfix) with ESMTP
	id 736DA157F4; Tue, 17 Aug 1999 14:12:11 -0700 (PDT)
	(envelope-from wrstuden@marcy.nas.nasa.gov)
Received: from localhost (wrstuden@localhost)
	by marcy.nas.nasa.gov (8.9.3/NAS8.8.7) with SMTP id OAA29074;
	Tue, 17 Aug 1999 14:12:22 -0700 (PDT)
Date: Tue, 17 Aug 1999 14:12:22 -0700 (PDT)
From: Bill Studenmund <wrstuden@nas.nasa.gov>
To: Michael Hancock <michaelh@cet.co.jp>
Cc: Terry Lambert <tlambert@primenet.com>, Hackers@FreeBSD.ORG,
	fs@FreeBSD.ORG
Subject: Re: BSD XFS Port & BSD VFS Rewrite
In-Reply-To: <Pine.BSF.3.95LJ1.1b3.990818055720.18717A-100000@sv01.cet.co.jp>
Message-ID: <Pine.SOL.3.96.990817141101.22897B-100000@marcy.nas.nasa.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 18 Aug 1999, Michael Hancock wrote:

> Interesting, have you read the Heidemann paper that outlines a solution
> that uses a cache manager?
> 
> You can probably find it somewhere here,
> http://www.isi.edu/~johnh/SOFTWARE/UCLA_STACKING/

Nope. I've read his dissertation, and his discussion of the lock
management inspired the struct lock * work I did for NetBSD (we use the
address of the lock, not the vnode, but other than that it's the same).

Thanks for the ref!

Take care,

Bill



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message