From: Jakob Oestergaard <jakob@unthought.net>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: NFS client (10x) performance regression 2.6.14.7 -> 2.6.15
Date: Fri, 31 Mar 2006 16:57:26 +0200 [thread overview]
Message-ID: <20060331145726.GL9811@unthought.net> (raw)
In-Reply-To: <20060331144951.GA9207@ti64.telemetry-investments.com>
On Fri, Mar 31, 2006 at 09:49:51AM -0500, Bill Rugolsky Jr. wrote:
...
> Jakob,
>
> Your NFS setup is specific to your system.
True. But it is my impression that this is a problem isolated on the
client side (am I wrong?)
> Have you considered trying this
> over loopback to narrow down the variables?
Do you mean NFS exporting a local filesystem, NFS mounting it again on
the local host? Or do you mean something with loopback mounts?
(Sorry if that's a stupid question, but I just need to know what you
mean :)
> If you see similar getattr/write
> behavior over loopback, it will make it easy for everyone else to test.
True.
I've currently tried compiling the kernel with three different gcc
versions to see if that made any change. It didn't. And I tried SMP
versus UP, again no difference. I'm just about to try HIGHMEM vs no
HIGHMEM...
Thanks for your suggestion - I will try it, if you tell me precisely
what you mean in the above :)
--
/ jakob
next prev parent reply other threads:[~2006-03-31 14:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 9:48 NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Jakob Oestergaard
2006-03-31 11:22 ` NFS client regression, simple test program Jakob Oestergaard
2006-03-31 12:22 ` NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Trond Myklebust
2006-03-31 12:45 ` Jakob Oestergaard
2006-03-31 13:06 ` Trond Myklebust
2006-03-31 13:21 ` Jakob Oestergaard
2006-03-31 13:44 ` Trond Myklebust
2006-03-31 14:08 ` Jakob Oestergaard
2006-03-31 14:21 ` Trond Myklebust
2006-03-31 14:35 ` Jakob Oestergaard
2006-03-31 14:49 ` Bill Rugolsky Jr.
2006-03-31 14:57 ` Jakob Oestergaard [this message]
2006-03-31 15:04 ` Bill Rugolsky Jr.
2006-03-31 15:24 ` Jakob Oestergaard
2006-03-31 16:35 ` Bill Rugolsky Jr.
2006-03-31 18:52 ` Jakob Oestergaard
2006-03-31 15:55 ` Trond Myklebust
2006-03-31 16:04 ` Jakob Oestergaard
2006-04-03 15:26 ` Jakob Oestergaard
2006-04-03 15:41 ` Trond Myklebust
2006-04-03 15:45 ` Jakob Oestergaard
2006-04-04 9:22 ` Jakob Oestergaard
2006-04-24 22:03 ` Trond Myklebust
2006-04-25 8:08 ` Jakob Oestergaard
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=20060331145726.GL9811@unthought.net \
--to=jakob@unthought.net \
--cc=brugolsky@telemetry-investments.com \
--cc=linux-kernel@vger.kernel.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