From: Andrew Morton <akpm@linux-foundation.org>
To: David Flynn <davidf+nntp@woaf.net>
Cc: linux-kernel@vger.kernel.org, "Ray Lee" <ray-lk@madrabbit.org>,
"Trond Myklebust" <trond.myklebust@fys.uio.no>,
pkpatel.lists@gmail.com, linux-nfs@vger.kernel.org,
Netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.26.3 kernel - progressive slowdown over NFS
Date: Wed, 10 Dec 2008 13:26:28 -0800 [thread overview]
Message-ID: <20081210132628.55991b93.akpm@linux-foundation.org> (raw)
In-Reply-To: <slrngjt7b4.d62.davidf+nntp@dog.thdo.woaf.net>
(cc's restored)
Please always do reply-to-all when working with kernel people. It's
important.
Thanks.
On Tue, 9 Dec 2008 16:31:32 +0000 (UTC)
David Flynn <davidf+nntp@woaf.net> wrote:
> On 2008-09-10, Priyank Patel <pkpatel.lists@gmail.com> wrote:
> > We have a simple python program which keeps running a C loop to lstat
> > NFS mounted directories. We are seeing some weird behavior w.r.t. the
> > run-time of this program on 2.6.26.3 kernel vs 2.6.24 kernel.
> >
> > The run-time of the following code increases over time on the 2.6.26.3
> > kernel, whereas remains flat (as expected) on the 2.6.24 kernel.
>
> I'm seeing a similar effect, and ran a benchmark pre and post reboot:
>
> $ strace -T /usr/sbin/bonnie++ -d . -s 0 -f -n 1 >/tmp/bonnie-r44237-netslow 2>&1
> ...reboot...
> $ strace -T /usr/sbin/bonnie++ -d . -s 0 -f -n 1 >/tmp/bonnie-r44237-netfast 2>&1
>
> Graphs of the operations are avaliable:
> http://davidf.woaf.net/nfsfail-2.6.26/
>
> In particular http://davidf.woaf.net/nfsfail-2.6.26/r44237-stat.pdf
>
> r44237-* was a machine with a 28 day uptime and
> r44088-* is an identical machine with 14 day uptime.
>
> The graphs show times as recorded by strace for each syscall (points), a
> cumulative frequency plot is also drawn on the same graph (lines).
> yellow-orange points/lines are before the reboot, purple afterwards.
>
> The machines are part of a cluster with a r/o nfsroot and common debian
> stock kernel:
> Linux r44088 2.6.26-1-amd64 #1 SMP Sat Aug 2 11:15:08 GMT 2008 x86_64 GNU/Linux
>
> Other nfs filesystems are also mounted; all nfs mounts are nfsv3 over udp.
>
> Has this issue been identified or resolved in 2.6.27?
>
> Extra logs can be provided if required.
>
> ..david
next prev parent reply other threads:[~2008-12-10 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 0:47 2.6.26.3 kernel - progressive slowdown over NFS Priyank Patel
2008-09-11 20:17 ` Priyank Patel
2008-12-09 16:31 ` David Flynn
2008-12-10 21:26 ` Andrew Morton [this message]
2008-12-10 0:38 ` Fwd: " Ray Lee
2008-12-10 1:06 ` Trond Myklebust
2008-12-10 1:12 ` Ray Lee
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=20081210132628.55991b93.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidf+nntp@woaf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkpatel.lists@gmail.com \
--cc=ray-lk@madrabbit.org \
--cc=trond.myklebust@fys.uio.no \
/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