public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client (10x) performance regression 2.6.14.7 -> 2.6.15
Date: Fri, 31 Mar 2006 18:04:27 +0200	[thread overview]
Message-ID: <20060331160426.GN9811@unthought.net> (raw)
In-Reply-To: <1143820520.8096.24.camel@lade.trondhjem.org>

On Fri, Mar 31, 2006 at 10:55:20AM -0500, Trond Myklebust wrote:
...
> No. They are the nfsstat numbers + timing information. I was interested
> in seeing if the latter can show up something.

Oops sorry. Here you go:

device sparrow:/exported/joe mounted on /u/joe with
fstype nfs statvers=1.0
 opts: rw,vers=3,rsize=32768,wsize=32768,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,hard,intr,proto=udp,timeo=7,retrans=3
 age:    2526
 caps: caps=0x1,wtmult=4096,dtsize=4096,bsize=0,namelen=255
 sec:    flavor=1
 events: 854 472 4017 4651 56 74 753 8357 3987 3511 0 4016 20 19 20 2 0 56 0 5 4371 0 0 0 0 
 bytes:  131161418 19867448 0 0 114028223 19862777 31282 4349 
 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
 xprt:   udp 1023 0 560 560 0 1832 176
 per-op statistics
  NULL: 1 1 0 0 24 0 0 0
  GETATTR: 115 115 0 0 12880 0 16 24
  SETATTR: 0 0 0 0 0 0 0 0
  LOOKUP: 149 149 0 0 21540 4 28 32
  ACCESS: 97 97 0 0 11640 0 8 8
  READLINK: 2 2 0 0 272 0 0 0
  READ: 193 193 0 0 5977864 176 424 600
  ... all zeroes ...
  READDIRPLUS: 2 2 0 0 6544 0 0 0
  FSSTAT: 0 0 0 0 0 0 0 0
  FSINFO: 1 1 0 0 80 0 4 4
  PATHCONF: 0 0 0 0 0 0 0 0
  COMMIT: 0 0 0 0 0 0 0 0

I'll be offline for a few hours - will check back later tonight.

-- 
/ jakob


  reply	other threads:[~2006-03-31 16:04 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
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 [this message]
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=20060331160426.GN9811@unthought.net \
    --to=jakob@unthought.net \
    --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