From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from verein.lst.de ([213.95.11.211]:60547 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754448AbaIZQmA (ORCPT ); Fri, 26 Sep 2014 12:42:00 -0400 Date: Fri, 26 Sep 2014 18:41:58 +0200 From: Christoph Hellwig To: Trond Myklebust Cc: Linux NFS Mailing List Subject: Re: [PATCH] pnfs/blocklayout: serialize GETDEVICEINFO calls Message-ID: <20140926164158.GA27296@lst.de> References: <1411740170-18611-1-git-send-email-hch@lst.de> <1411740170-18611-2-git-send-email-hch@lst.de> <20140926154843.GA22675@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Fri, Sep 26, 2014 at 12:21:06PM -0400, Trond Myklebust wrote: > > Not without getting rid of the rpc_pipefs interface. That is on my > > very long term TODO list, but it will require new userspace support. > > Why is that? rpc_pipefs was designed to be message based, so it should > work quite well in a multi-threaded environment. We certainly don't > use mutexes around the gssd up/downcall, and the only reason for the > mutex in idmapd is to deal with the keyring upcall. Ok, the GSS code dynamically allocates a new message for each upcall and thus doesn't have the issue. I'll take a look if I can do this in the blocklayout driver as well.