From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH] AFS: Implement file locking [try #2] Date: Thu, 31 May 2007 10:41:37 +0100 Message-ID: <24732.1180604497@redhat.com> References: <20070530180309.GG7736@fieldses.org> <20070529215736.GO6815@fieldses.org> <20070529145426.19366.35289.stgit@warthog.cambridge.redhat.com> <32087.1180514132@redhat.com> Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: "J. Bruce Fields" Return-path: Received: from mx1.redhat.com ([66.187.233.31]:33025 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756858AbXEaJl6 (ORCPT ); Thu, 31 May 2007 05:41:58 -0400 In-Reply-To: <20070530180309.GG7736@fieldses.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org J. Bruce Fields wrote: > > Yes. I need to get the server lock first, before going to the VFS locking > > routines. > > That doesn't really answer the question. The NFS client has similar > requirements, but it doesn't have to duplicate the per-inode lists of > granted locks, for example. Actually, it might... It's just that they're in the lock manager server, not in the NFS client. As far as I can tell, NFS passes each lock request individually to the lock manager server, which grants them individually. AFS doesn't do that. David