Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp3835134pxa; Sun, 9 Aug 2020 13:28:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyAyANejzw0SOAEeI9IO6phvkDaw0WmMxKef7zZre4kKGgpYcBNH4otnwgw+1HjYxLoCZrI X-Received: by 2002:aa7:c0d8:: with SMTP id j24mr18647049edp.338.1597004906685; Sun, 09 Aug 2020 13:28:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597004906; cv=none; d=google.com; s=arc-20160816; b=u4+iZ8uJSgVa1kCrp8j6+y4sXBOsAQPXqG+EX3FvzC2z9VMdiiS4Btvf12MfknSpZ6 Jv4zTK7hw91tvwxm88yszJEK6mES8YykjAu6GsrAXy9oMR1IUYS7PamM2gqiUi4mmCUw KCbUsALGIjgo+OJx0G8/nj2eTlb1s8JxV3buI1fpc4vP609sv75YW9BiI9fcfXWFjQXn Yc+0g6PnO9IdSzUhSYWc8zzdik0gXmRxsNFnHGaTzk6RT3LE3q19wFC99OIbwcqpBQYL RMbTLpqrdLp8y6P2u7EpzbC0fHN6/zCRoNhOfy81bjnhBk9td5qui1hOs0Bi739lgM5M Tn5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-filter; bh=RmGACZZZQ1527G5ocrb6UZaQEA8gJh1S3mqOpgsULNk=; b=AAMX8dKVT6+O7Sfc9fVJZUX3YfF361lD3GvejLzw33mAkm5Bi6iXI40L1V8wfyS6zA NiqFb9NZtNPm5HnwXGkS2lVe1cidRPpJZOInfQnsUrgEEflSpTUgVf4wVPPli8tn/mPV VmoBm0j0cStY0DqJySXU8J0nLiEAGsAAUc8zfzPBHbLGRAA/n/5t1t2fcB74h0b55oF5 Ag5cbE6qHsO5fHoGNqrRmDt11MPCPhOfcPRbcslm0osmuGOqkCarpN2ZiTnNyb/VVsFN Bx7HzwqKKTsu3VjYjDT+o9/fSLmsPN9+YqT3pCzffm1fml3atbf4Qu0UU9rFEYP/s55f v2Jw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@fieldses.org header.s=default header.b=qQe9n9xY; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s23si8983223edy.158.2020.08.09.13.27.44; Sun, 09 Aug 2020 13:28:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@fieldses.org header.s=default header.b=qQe9n9xY; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726299AbgHIU1n (ORCPT + 99 others); Sun, 9 Aug 2020 16:27:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726296AbgHIU1n (ORCPT ); Sun, 9 Aug 2020 16:27:43 -0400 Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBF31C061756 for ; Sun, 9 Aug 2020 13:27:42 -0700 (PDT) Received: by fieldses.org (Postfix, from userid 2815) id 536DE69C3; Sun, 9 Aug 2020 16:27:39 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 536DE69C3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1597004859; bh=RmGACZZZQ1527G5ocrb6UZaQEA8gJh1S3mqOpgsULNk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qQe9n9xYldBLGwi+S1Pj7JewELTwBR24a64ZkBR/hdcyCj2wVEiw7uHR6so4wkZsQ QMiBJ0w3zW43ISWkeHUR8/NgNK30CBqSQv+OYH4Bf94GsPJOfZCphrncPpiae89wVL ZyPLfwcep8yTC+KA64c3kjayUontuVetIn78Viyo= Date: Sun, 9 Aug 2020 16:27:39 -0400 From: Bruce Fields To: Chuck Lever Cc: Linux NFS Mailing List Subject: Re: still seeing single client NFS4ERR_DELAY / CB_RECALL Message-ID: <20200809202739.GA29574@fieldses.org> References: <139C6BD7-4052-4510-B966-214ED3E69D61@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <139C6BD7-4052-4510-B966-214ED3E69D61@oracle.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Sun, Aug 09, 2020 at 01:11:36PM -0400, Chuck Lever wrote: > Hi Bruce- > > I noticed that one of my tests takes about 4x longer on NFSv4.0 than > it does on NFSv3 or NFSv4.[12]. As an initial stab at the cause, I'm > seeing lots of these: Oops, looks obvious in retrospect, but I didn't think of it. In the 4.1+ case, sessions mean that we know which client every operation comes from. In the 4.0 case that only works for operations that take a stateid or something else we can link back to a client. That means in the 4.0 case delegations are less useful, since they have to be broken on any (non-truncating) setattr, any link/unlink, etc., even if the operation comes from the same client--the server doesn't have a way to know that. Maybe the change to give out read delegations even on write opens probably just isn't worth in the 4.0 case. --b. > > <...>-283894 [003] 4060.507314: nfs4_xdr_status: > task:51308@5 xid=0x1ec806a9 error=-10008 (DELAY) > operation=34 <...>-283894 [003] 4060.507338: nfs4_setattr: > error=-10008 (DELAY) fileid=00:27:258012 fhandle=0x25ef273d > stateid=0:0x7bd5c66f <...>-283982 [006] 4060.508134: > nfs4_state_mgr: hostname=klimt.ib clp > state=CHECK_LEASE|0x4020 NFSv4-6239 [007] 4060.508137: > nfs4_cb_recall: error=0 (OK) fileid=00:27:258012 > fhandle=0x25ef273d stateid=1:0x910c8d4c dstaddr=klimt.ib > > The workload is the git regression suite, which I run like this on a > single client: > > --- mount test export --- > > $ cd /mnt; rm -rf git*; tar zvxf ~/Downloads/git-2.23.0.tar.gz > > --- remount test export --- > > $ cd /mnt/git*; make clean; make -j12 > > --- remount test export --- > > $ cd /mnt/git*; make -j12 test > > -- Chuck Lever > >