From: Michael Tokarev <mjt@tls.msk.ru>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Linux-kernel <linux-kernel@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: 3.0+ NFS issues (bisected)
Date: Sat, 18 Aug 2012 16:58:31 +0400 [thread overview]
Message-ID: <502F9177.5060100@msgid.tls.msk.ru> (raw)
In-Reply-To: <20120818111354.GA16611@fieldses.org>
On 18.08.2012 15:13, J. Bruce Fields wrote:
> On Sat, Aug 18, 2012 at 10:49:31AM +0400, Michael Tokarev wrote:
[]
>> Well. What can I say? With the change below applied (to 3.2 kernel
>> at least), I don't see any stalls or high CPU usage on the server
>> anymore. It survived several multi-gigabyte transfers, for several
>> hours, without any problem. So it is a good step forward ;)
>>
>> But the whole thing seems to be quite a bit fragile. I tried to follow
>> the logic in there, and the thing is quite a bit, well, "twisted", and
>> somewhat difficult to follow. So I don't know if this is the right
>> fix or not. At least it works! :)
>
> Suggestions welcomed.
Ok...
Meanwhile, you can add my
Tested-By: Michael Tokarev <mjt@tls.msk.ru>
to the patch.
>> And I really wonder why no one else reported this problem before.
>> Is me the only one in this world who uses linux nfsd? :)
>
> This, for example:
>
> http://marc.info/?l=linux-nfs&m=134131915612287&w=2
>
> may well describe the same problem.... It just needed some debugging
> persistence, thanks!
Ah. I tried to find something when I initially
sent this report, but weren't able to. Apparently
I'm not alone with this problem indeed!
Thank you for all the work!
/mjt
prev parent reply other threads:[~2012-08-18 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 6:53 3.0+ NFS issues Michael Tokarev
2012-05-29 15:24 ` J. Bruce Fields
2012-05-30 7:11 ` Michael Tokarev
2012-05-30 13:25 ` J. Bruce Fields
2012-05-31 6:47 ` Michael Tokarev
2012-05-31 12:59 ` Myklebust, Trond
2012-05-31 13:24 ` Michael Tokarev
2012-05-31 13:46 ` Myklebust, Trond
2012-05-31 13:51 ` Michael Tokarev
2012-07-10 12:52 ` Michael Tokarev
2012-07-12 12:53 ` J. Bruce Fields
2012-08-17 1:56 ` 3.0+ NFS issues (bisected) Michael Tokarev
2012-08-17 14:56 ` J. Bruce Fields
2012-08-17 16:00 ` J. Bruce Fields
2012-08-17 17:12 ` Michael Tokarev
2012-08-17 17:18 ` J. Bruce Fields
2012-08-17 17:26 ` Michael Tokarev
2012-08-17 17:29 ` Michael Tokarev
2012-08-17 19:18 ` J. Bruce Fields
2012-08-17 20:08 ` J. Bruce Fields
2012-08-17 22:32 ` J. Bruce Fields
2012-08-18 6:49 ` Michael Tokarev
2012-08-18 11:13 ` J. Bruce Fields
2012-08-18 12:58 ` Michael Tokarev [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=502F9177.5060100@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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