Re: Tracing down 250ms open/chdir calls

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Carsten Aulbert <carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	beowulf-r+SMWMTQ9DpAfugRpC6u6w@public.gmane.org
Subject: Re: Tracing down 250ms open/chdir calls
Date: Mon, 16 Feb 2009 14:00:48 +0100	[thread overview]
Message-ID: <49996380.1090902@aei.mpg.de> (raw)
In-Reply-To: <1234788998.7708.40.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

Hi Trond,

Trond Myklebust schrieb:
> 2.6.27.7 has a known NFS client performance bug due to a change in the
> authentication code. The fix was merged in 2.6.27.9: see the commit
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git&a=commitdiff&h=a0f04d0096bd7edb543576c55f7a0993628f924a

Maybe that's also a reason why we don't see it that often anymore -
although the user load has shifted a bit also. We are running 2.7.27.14
(and .15 since Friday).

Thanks for letting me know, I'll probably re-run the tests again with a
newer kernel.

Cheers

Carsten

WARNING: multiple messages have this Message-ID (diff)

From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	beowulf@beowulf.org
Subject: Re: Tracing down 250ms open/chdir calls
Date: Mon, 16 Feb 2009 14:00:48 +0100	[thread overview]
Message-ID: <49996380.1090902@aei.mpg.de> (raw)
In-Reply-To: <1234788998.7708.40.camel@heimdal.trondhjem.org>

Hi Trond,

Trond Myklebust schrieb:
> 2.6.27.7 has a known NFS client performance bug due to a change in the
> authentication code. The fix was merged in 2.6.27.9: see the commit
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git&a=commitdiff&h=a0f04d0096bd7edb543576c55f7a0993628f924a

Maybe that's also a reason why we don't see it that often anymore -
although the user load has shifted a bit also. We are running 2.7.27.14
(and .15 since Friday).

Thanks for letting me know, I'll probably re-run the tests again with a
newer kernel.

Cheers

Carsten

next prev parent reply	other threads:[~2009-02-16 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  7:55 Tracing down 250ms open/chdir calls Carsten Aulbert
2009-02-16 12:56 ` Trond Myklebust
     [not found]   ` <1234788998.7708.40.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-16 13:00     ` Carsten Aulbert [this message]
2009-02-16 13:00       ` Carsten Aulbert
2009-02-16 13:24 ` Joe Landman
2009-02-16 13:44   ` Carsten Aulbert

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=49996380.1090902@aei.mpg.de \
    --to=carsten.aulbert-l1a6w7hxd2yelga04laivw@public.gmane.org \
    --cc=beowulf-r+SMWMTQ9DpAfugRpC6u6w@public.gmane.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.