From owner-freebsd-current  Wed Sep 17 19:08:43 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA27119
          for current-outgoing; Wed, 17 Sep 1997 19:08:43 -0700 (PDT)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27112
          for <current@freebsd.org>; Wed, 17 Sep 1997 19:08:40 -0700 (PDT)
Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id TAA06514; Wed, 17 Sep 1997 19:08:40 -0700 (PDT)
Date: Wed, 17 Sep 1997 19:08:40 -0700 (PDT)
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <199709180208.TAA06514@kithrup.com>
To: current@freebsd.org
Subject: Re: NFS client locking
Newsgroups: kithrup.freebsd.current
In-Reply-To: <199709122209.PAA29030.kithrup.freebsd.current@usr08.primenet.com>
Organization: Kithrup Enterprises, Ltd.
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199709122209.PAA29030.kithrup.freebsd.current@usr08.primenet.com> you write:
>In order to implement this, the common locking code must move out
>of the per FS VOP_ADVLOCK() and into the system calls/VFS framework
>layer.

For what it's worth, I've seen Terry's code to do this and (unless he's gone
and changed it again, sly get that he is :)), it was reasonable and not
terribly complicated.  Mostly grunt work, I think.