--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 29, 2006 at 08:56:43AM -0700, Jason Thorpe wrote:
>=20
> On Jun 29, 2006, at 3:08 AM, Juergen Hannken-Illjes wrote:
>=20
> >- We add a transaction lock to "struct mount" behaving like a =20
> >lockmgr lock
> >  but allowing a "already have a shared lock" query.
> >
> >- Transactions are enclosed in vn_trans_lock/vn_trans_unlock pairs =20
> >like
>=20
> Uh, why not make it a normal reader-writer lock and always pair a =20
> release with an acquire?  That way you can do away with the "1 of the =20
> read already owns a shared lock".

This was in response to my comments, which in turn were a response to=20
comments you made many moons ago decrying recursive locking in our file=20
systems. :-)

Take care,

Bill

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFEpIg3Wz+3JHUci9cRAkPEAJ0TL89zt6LxS4tNsr61XsxeWuxyWgCgg2mI
Rn2grJPA7HeChEBv1xv5G9g=
=vpJp
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--