Re: [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage

From: Chuck Lever
Date: Wed Jul 25 2018 - 10:32:20 EST

> On Jul 25, 2018, at 9:27 AM, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
> On 18 June 2018 at 18:20, Chuck Lever <chuck.lever@xxxxxxxxxx> 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