From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>,
Daniel Wagner <wagi@monom.org>, <linux-nfs@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] NFS: Use complete() instead complete_all()
Date: Mon, 26 Sep 2016 09:31:54 -0400 [thread overview]
Message-ID: <ded5c166-aa7e-ce61-8190-ffc15c7d1b12@Netapp.com> (raw)
In-Reply-To: <74468e19-772d-41b8-b7df-c0aa845e52ab@bmw-carit.de>
On 09/26/2016 01:33 AM, Daniel Wagner wrote:
> Hi Anna,
>
> On 09/23/2016 03:48 PM, Anna Schumaker wrote:
>>> Besides trying to analys all the code paths to the wait_for_completion()
>>> call and convince myself that there is only one waiter, I also run
>>> a few tests:
>>>
>>> - some fio benchmarks
>>> - pynfs
>>> -cthon04
>>
>> Thanks for the patches, and for the extensive testing! I haven't
>> tried them with xfstests yet, but They look okay to me otherwise.
>> Assuming I don't see any new failures there I'll plan on adding them
>> for v4.9.
>
> I tried a few tests from xfstests but I was not sure which make sense to run, that's why I went for the more NFS specific tests.
>
> I'll see what happens when I run the generic tests from xfstests. Should all of them pass?
No, there are a handful that we know don't pass. When I run on NFS v4.1, I get:
Failures: generic/035 generic/071 generic/128 generic/294 generic/306 generic/309 generic/310 generic/313 generic/314 generic/315 generic/316 generic/319 generic/337 generic/360 generic/375
Failed 15 of 92 tests
Thanks,
Anna
>
> cheers,
> daniel
next prev parent reply other threads:[~2016-09-26 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 11:54 Daniel Wagner
2016-09-22 11:54 ` [PATCH 1/2] NFS: direct: use complete() instead of complete_all() Daniel Wagner
2016-09-22 11:54 ` [PATCH 2/2] NFS: cache_lib: " Daniel Wagner
2016-09-23 13:48 ` [PATCH 0/2] NFS: Use complete() instead complete_all() Anna Schumaker
2016-09-26 5:33 ` Daniel Wagner
2016-09-26 13:31 ` Anna Schumaker [this message]
2016-09-27 7:42 ` Daniel Wagner
2016-09-27 8:33 ` Daniel Wagner
2016-09-27 17:15 ` Anna Schumaker
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=ded5c166-aa7e-ce61-8190-ffc15c7d1b12@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=wagi@monom.org \
/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
all inboxes | Powered by JetHome®