Messages in this thread | | | From | Krzysztof Kozlowski <> | Date | Wed, 25 Jul 2018 15:27:46 +0200 | Subject | Re: [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage |
| |
On 18 June 2018 at 18:20, Chuck Lever <chuck.lever@oracle.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
| |