[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9B9E1627-AC2E-4A0C-AB6E-5815876A59AB@oracle.com>
Date: Wed, 25 Jul 2018 10:31:54 -0400
From: Chuck Lever <chuck.lever@...cle.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Trond Myklebust <trondmy@...merspace.com>,
"sudeep.holla@....com" <sudeep.holla@....com>,
Trond Myklebust <trond.myklebust@...marydata.com>,
Anna Schumaker <anna.schumaker@...app.com>,
Bruce Fields <bfields@...ldses.org>,
Jeff Layton <jlayton@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Linux NFS Mailing List <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 Jul 25, 2018, at 9:27 AM, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>
> 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?
Hi Krzysztof, I don't know of any recent changes. Bisecting would be
a good place to start.
--
Chuck Lever
Powered by blists - more mailing lists