[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJKOXPfMiaGP9xqPcOQMs+a4RKvhK03v51e5r3GaUiFs0G=61Q@mail.gmail.com>
Date: Wed, 25 Jul 2018 15:27:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Trond Myklebust <trondmy@...merspace.com>,
"sudeep.holla@....com" <sudeep.holla@....com>,
Trond Myklebust <trond.myklebust@...marydata.com>,
Anna Schumaker <anna.schumaker@...app.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
Jeff Layton <jlayton@...nel.org>,
"David S. Miller" <davem@...emloft.net>, linux-nfs@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>
Subject: Re: [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage
On 18 June 2018 at 18:20, Chuck Lever <chuck.lever@...cle.com> wrote:
>
> The extra serialization appears to have a reproducible performance
> impact on RDMA, which no longer takes the reserve_lock when allocating
> a slot.
>
> I could put an xprt_alloc_xid call in xprt_alloc_slot, but that would
> only work for socket-based transports. Would it be OK if RDMA had its
> own XID allocation mechanism?
Hi,
On recent next the issue appeared again. My boards with NFSv4 root
timeout on 80% of boots. This time my NFS server is faster - Pi3 B+
:).
Is this know? Should I start long bisect or maybe you can point me to
possible causes?
Best regards,
Krzysztof
Powered by blists - more mailing lists