From: Chuck Lever <chuck.lever@oracle.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Bruce Fields <bfields@fieldses.org>,
Jeff Layton <jlayton@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage
Date: Thu, 26 Jul 2018 21:48:06 -0400 [thread overview]
Message-ID: <63E567B6-ACC6-449F-95F6-1F17102221F1@oracle.com> (raw)
In-Reply-To: <CAJKOXPejStfaQdtUwh33v+aC7KpamoLkix3nitbHrDRx4QAR6g@mail.gmail.com>
> On Jul 26, 2018, at 4:46 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 25 July 2018 at 16:31, Chuck Lever <chuck.lever@oracle.com> wrote:
>>
>>
>>> On Jul 25, 2018, at 9:27 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>
>>> 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?
>>
>> Hi Krzysztof, I don't know of any recent changes. Bisecting would be
>> a good place to start.
>
> Hi,
>
> That was my mistake because of missing part of NFS server
> configuration on new board. I tested again recent releases and current
> linux-next and everything works fine.
>
> Sorry for the noise.
Thanks for the update.
--
Chuck Lever
prev parent reply other threads:[~2018-07-27 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 11:19 [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage Krzysztof Kozlowski
2018-06-07 11:22 ` Krzysztof Kozlowski
2018-06-15 12:53 ` Sudeep Holla
2018-06-15 14:07 ` Krzysztof Kozlowski
2018-06-15 14:10 ` Krzysztof Kozlowski
2018-06-15 14:23 ` Chuck Lever
2018-06-15 14:28 ` Krzysztof Kozlowski
[not found] ` <CAJKOXPf7V1z4pNZ2RsjkJmaVAgk34_rPOtQOc7J5KRMSRemrdg@mail.gmail.com>
[not found] ` <082848F5-6360-4523-BA95-601777E17CF2@oracle.com>
[not found] ` <CAJKOXPe4uqOZGd_zb_Mqq4Fspu63LHZky86O4tPaD3BZNCBS6w@mail.gmail.com>
[not found] ` <6AAC5897-8762-4209-8718-67291B87AA00@oracle.com>
[not found] ` <d617f8a85c3414230cd755fe0e4470c0f8bd17ff.camel@hammerspace.com>
[not found] ` <26995E49-E8DD-421D-BABF-9E672B9383BD@oracle.com>
[not found] ` <30a1455b6817361f8228c022628aef5cdee70c3e.camel@hammerspace.com>
[not found] ` <784782B0-A387-4D3B-A517-E85D851162B8@oracle.com>
2018-07-25 13:27 ` Krzysztof Kozlowski
2018-07-25 14:31 ` Chuck Lever
2018-07-26 8:46 ` Krzysztof Kozlowski
2018-07-27 1:48 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63E567B6-ACC6-449F-95F6-1F17102221F1@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=jlayton@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=trond.myklebust@primarydata.com \
--cc=trondmy@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).