From owner-cvs-src@FreeBSD.ORG  Wed May 14 06:50:41 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 827FA37B401; Wed, 14 May 2003 06:50:41 -0700 (PDT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 31D5D43F93; Wed, 14 May 2003 06:50:41 -0700 (PDT)
	(envelope-from rwatson@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h4EDoe0U023265;
	Wed, 14 May 2003 06:50:40 -0700 (PDT)
	(envelope-from rwatson@repoman.freebsd.org)
Received: (from rwatson@localhost)
	by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h4EDoeVv023264;
	Wed, 14 May 2003 06:50:40 -0700 (PDT)
Message-Id: <200305141350.h4EDoeVv023264@repoman.freebsd.org>
From: Robert Watson <rwatson@FreeBSD.org>
Date: Wed, 14 May 2003 06:50:40 -0700 (PDT)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/usr.sbin/rpc.lockd lock_proc.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2003 13:50:42 -0000

rwatson     2003/05/14 06:50:40 PDT

  FreeBSD src repository

  Modified files:
    usr.sbin/rpc.lockd   lock_proc.c 
  Log:
  When receiving NLM_GRANTED_RES or NLM4_GRANTED_RES lock granted messages
  from the NFS server, following contention on a lock by this or another
  client, immediately notify the waiting process that the lock has been
  granted via a wakeup.  Without this change, the client rpc.lockd will
  not wakeup the waiting process until it next re-polls the lock (sometime
  in the next ten seconds), which can lead to marked latency across all
  potential lockers, as the lock is held by the client for the duration.
  
  Approved by:    re (scottl)
  Submitted by:   truckman
  Reviewed by:    Andrew P. Lentvorski, Jr <bsder@allcaps.org>
  
  Revision  Changes    Path
  1.11      +7 -2      src/usr.sbin/rpc.lockd/lock_proc.c