From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>, pkpatel.lists@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: Fwd: 2.6.26.3 kernel - progressive slowdown over NFS
Date: Tue, 9 Dec 2008 17:12:46 -0800 [thread overview]
Message-ID: <2c0942db0812091712l5efa2d2dia9ff2e3d92f81bbc@mail.gmail.com> (raw)
In-Reply-To: <1228871206.30231.76.camel@heimdal.trondhjem.org>
[ sigh, adding back original reporter. Oops. -- rbl ]
Priyank Patel, please see Trond's response below and try out the
suggested patch linked below.
On Tue, Dec 9, 2008 at 5:06 PM, Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> On Tue, 2008-12-09 at 16:38 -0800, Ray Lee wrote:
>> [ adding netdev, linux-nfs to cc: -- rbl ]
>>
>> Hi,
>>
>>
>> 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.
>> [See attached graphs - B1.jpg and B2.jpg] Once the 2.6.26.3 machine
>> gets into this state, we need to restart the box to get back to
>> reasonable run-times. Is this a known issue ?
>
> Could you try applying the following patch?
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=23918b03060f6e572168fdde1798a905679d2e06
>
> Trond
>
> PS: note that your 2.6.26 config file has _very_ different memory models
> and kernel debugging options enabled compared to your 2.6.24 kernel.
> That may also affect performance.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2008-12-10 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 0:47 Priyank Patel
2008-09-11 20:17 ` Priyank Patel
2008-12-09 16:31 ` David Flynn
2008-12-10 21:26 ` Andrew Morton
2008-12-10 0:38 ` Fwd: " Ray Lee
2008-12-10 1:06 ` Trond Myklebust
2008-12-10 1:12 ` Ray Lee [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=2c0942db0812091712l5efa2d2dia9ff2e3d92f81bbc@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkpatel.lists@gmail.com \
--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
all inboxes | Powered by JetHome®