public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Max Kellermann <max@duempel.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	harry@atmos.washington.edu
Subject: Re: High load in 2.6.27, NFS / rpcauth_lookup_credcache()?
Date: Thu, 23 Oct 2008 10:55:45 -0400	[thread overview]
Message-ID: <1224773745.7625.4.camel@localhost> (raw)
In-Reply-To: <20081023123628.GA18549@squirrel.roonstrasse.net>

On Thu, 2008-10-23 at 14:36 +0200, Max Kellermann wrote:
> On 2008/10/22 11:12, Max Kellermann <max@duempel.org> wrote:
> > after I was able to fix http://lkml.org/lkml/2008/10/17/147, the
> > server which was already upgraded to 2.6.27.2 still gets very high
> > load.  It is a web server with NFS file storage (NetApp), and while
> > the others in the cluster (kernel 2.6.25) have a load of 1-3, 2.6.27.2
> > gets 30-50.
> > 
> > I did an oprofile, with the following results (server just started,
> > load "only" 5-10):
> > 
> > 87593    56.1116  (no location information)   vmlinux
> > vmlinux                  rpcauth_lookup_credcache
> > 16037    10.2732  auth_generic.c:0            vmlinux
> > vmlinux                  generic_match
> > 6460      4.1382  (no location information)   php4
> > php4                     (no symbols)
> > 2478      1.5874  (no location information)   libc-2.7.so
> > libc-2.7.so              (no symbols)
> > [...]
> > 
> > We havn't configured any special authentication method.  It is a NFSv3
> > over UDP mount, but the kernel has NFSv4 and therefore KRB5 enabled.
> > 
> > Any ideas why rpcauth_lookup_credcache() goes overboard with CPU
> > usage?
> 
> I have bisected the problem: 98a8e323 is the result ("SUNRPC: Add a
> helper rpcauth_lookup_generic_cred()").  5c691044 is ok.
> 
> See the attached oprofile annotation data for both commits.  I guess
> that the function rpcauth_lookup_credcache() is waiting for a spinlock
> too often and too long.  Trond, any idea?

Can you add a '-v' to the rpc.gssd daemon startup line? I'd like to see
how often you are creating new gss contexts.

> Harry: added you to Cc because your problem sounds similar.

Harry's problem is should be unrelated. afaik, he is seeing a problem
with userland RPC code, not kernel rpc code.

Trond


  reply	other threads:[~2008-10-23 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  9:12 High load in 2.6.27, NFS / rpcauth_lookup_credcache()? Max Kellermann
2008-10-22 17:56 ` J. Bruce Fields
2008-10-23 12:36 ` Max Kellermann
2008-10-23 14:55   ` Trond Myklebust [this message]
2008-10-24  8:39     ` Max Kellermann
2008-10-24 18:09       ` Trond Myklebust
2008-10-27  9:58         ` Max Kellermann
2008-10-27 15:48           ` Trond Myklebust
2008-11-17 12:35             ` Max Kellermann
2008-11-19 22:31               ` Trond Myklebust
2008-11-20 14:08                 ` Max Kellermann
2008-12-15 23:44     ` Harry Edmon
2008-12-16 13:02       ` Trond Myklebust
2008-12-16 21:21         ` Willy Tarreau
2008-12-16 23:21           ` [stable] " Greg KH

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=1224773745.7625.4.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=harry@atmos.washington.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=max@duempel.org \
    /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