From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: asynchronous locks for cluster exports Date: Thu, 7 Dec 2006 16:51:08 +0000 Message-ID: <20061207165108.GA21009@infradead.org> References: <11653832602203-git-send-email-bfields@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net, Marc Eshel Return-path: To: "J. Bruce Fields" Content-Disposition: inline In-Reply-To: <11653832602203-git-send-email-bfields@fieldses.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org On Wed, Dec 06, 2006 at 12:34:10AM -0500, J. Bruce Fields wrote: > We'd like an asynchronous posix locking interface so that we can provide NFS > - We added a new ->lock() export operation, figuring this was a feature > that only lockd and nfsd care about for now, and that we'd rather not > muck about with common locking code. But the export operation is > pretty much identical to the file ->lock() operation; would it make > more sense to use that? This definitly needs to be merged back into the ->lock file operation ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs