All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Kevin Constantine
	<Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: Exposing cache statistics
Date: Fri, 17 Apr 2009 07:05:19 -0400	[thread overview]
Message-ID: <49E8626F.6000508@RedHat.com> (raw)
In-Reply-To: <49E7CE3E.8020006-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>



Kevin Constantine wrote:
> Trond Myklebust wrote:
>> On Wed, 2009-04-15 at 13:30 -0700, Kevin Constantine wrote:
>>> Has there been any effort to expose caching statistics to the end
>>> user?   On the client-side, it would be useful to see how much data
>>> is being re-used from cache vs data that gets retrieved over the
>>> wire.  Similarly on the server side, it would be nice to see how much
>>> data is being served from cache vs having to pull the data from disk.
>>>
>>> Just wondering if anyone started anything to expose this sort of
>>> information.
>>
>> See the nfs-iostat tool in the nfs-utils package:
>>
>>   
>> http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=tree;f=tools/nfs-iostat;h=929e303cc762a68dfd01546f5150eb294274164e;hb=refs/heads/master
>>
>>
>> Note that you need a 2.6.17 kernel or newer.
>>
>> Cheers
>>   Trond
> 
> Thanks Trond-
> 
> It seems like nfs-iostat is displaying the number of pages that are
> being written to the read/write caches (i'm only looking at the
> client-side at the moment), and what I'm interested in is the ratio of
> pages being read from cache vs data being fetched from the server.
> 
> Is there any documentation on the layout of /proc/self/mountstats?
No, unfortunately not... 

steved.

  parent reply	other threads:[~2009-04-17 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 20:30 Exposing cache statistics Kevin Constantine
     [not found] ` <49E643CD.9070809-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-04-15 20:41   ` Trond Myklebust
     [not found]     ` <1239828092.5177.139.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-17  0:33       ` Kevin Constantine
     [not found]         ` <49E7CE3E.8020006-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-04-17 11:05           ` Steve Dickson [this message]
     [not found]             ` <49E8626F.6000508-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-17 12:54               ` Trond Myklebust
2009-04-17 15:58         ` Chuck Lever

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=49E8626F.6000508@RedHat.com \
    --to=steved@redhat.com \
    --cc=Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.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.