Subject: Re: CVS commit: src
To: YAMAMOTO Takashi <firstname.lastname@example.org>
From: Bill Studenmund <email@example.com>
Date: 06/20/2004 15:40:56
Content-Type: text/plain; charset=us-ascii
On Sun, Jun 20, 2004 at 02:15:24PM +0900, YAMAMOTO Takashi wrote:
> > Well, what else should he have done? He has to move the sleepers from o=
> > lock to another, given what he's doing (I looked hard at this at the ti=
> > it was added). At the time he decides to do the transfer, the sleepers =
> > ALREADY asleep on a lock. So there's no ffs-internal way to handle this=
> > the sleepers are already outside of the ffs code.
> i think that having some tricks in VOP_LOCK/UNLOCK/ISLOCKED is enough.
> (in addition to stopping exporting v_vnlock, of course.)
Please look at what he is doing. I do not see how tricks in VOP_LOCK &=20
friends will cover this. Or any tricks I can think of will add latency to=
common code paths, and I'd rather have this lock merging going on than=20
that dealy. ;-)
Also, what is wrong with exporting v_vnlock? It simplifies and economizes=
a lot of things.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----