Subject: Re: CVS commit: src
To: Gordon Waidhofer <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 06/24/2004 22:28:30
Content-Type: text/plain; charset=us-ascii
On Thu, Jun 24, 2004 at 08:58:19PM -0700, Gordon Waidhofer wrote:
> > In terms of getting to this, I think I'd much prefer moving to internal=
> > locking.
> I'd vote for that, I think. Does internal and
> advisory/non-exclusive mean the same thing?
I don't think so. Well, internal may mean the same thing as non-exclusive. =
Advisory, though, to me means something different. The file systems have a
choice as to what they do. I'm not giving file systems a choice in the
change I propose. ;-)
> > One of the bigest problems I encountered when getting layered=20
> > file systems working was ambiguity in what was was happeneing with=20
> > locking. So I pushed everything to use exclusive real locks; to be=20
> > consistent (and a bit facist). If we go to making locks advisory, I'm=
> > concerned that things would get ambiguous again, and we're back in a me=
> That helps explain things a lot. Thank you.
> I don't know anything about the layered file
> system stuff, but now I know what to worry about.
> I'll bet that's a good -- and illuminating -- war story.
Yeah. It was irritating.
My main thought is we should figure out what we're doing, and be forceful=
(aggressive, obnoxious) about making everything follow it. :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----