From: Greg Banks <gnb@melbourne.sgi.com>
To: Oliver Tennert <tennert@science-computing.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: PATCH [NFSd] NFSv3/TCP
Date: Fri, 07 May 2004 18:11:00 +1000 [thread overview]
Message-ID: <409B4494.5253316B@melbourne.sgi.com> (raw)
In-Reply-To: Pine.LNX.4.44.0405070949160.5549-100000@picard.science-computing.de
Oliver Tennert wrote:
>
> As it does not any changes for say a i386 architecture,
Yes, by design.
> I cannot see why
> after that my lockups should go away.
I don't claim any such thing, I was just resending a patch (which is of no
use to you) that Neil mentioned had been lost in the shuffle.
> Are lockups no known problem at all? Am I the only one experiencing them?
> They _definitely_ went away for me with NFSSVC_MAXBLKSIZE equal 32k, even
> under high IO pressure.
Sure, I believe you, I just have no idea what your problem is.
As a general statement of no particular import, I note that going to 32K
has a number of other side effects other than the obvious. For streaming
reads and writes the call rate goes down by a factor of 4 so you may be
not exercising some race condition. Also there may be different code paths
through READDIR and READDIR+ code.
Now if you had some kind of kernel debugger and could post some more
information, like process list and kernel stack traces from the hang,
someone (not me) may be able to figure out the real problem that you've
hidden by going to 32K.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-05-07 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0405070834001.4547-100000@picard.science-computing.de>
[not found] ` <16539.12572.90447.543633@cse.unsw.edu.au>
2004-05-07 7:22 ` PATCH [NFSd] NFSv3/TCP Greg Banks
2004-05-07 7:52 ` Oliver Tennert
2004-05-07 8:11 ` Greg Banks [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=409B4494.5253316B@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=tennert@science-computing.de \
/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