linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: stark-DPNOqEs/LNQ@public.gmane.org
To: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 1/2] VFS: New /proc file /proc/self/mountstats
Date: 13 Oct 2011 08:58:20 -0400	[thread overview]
Message-ID: <ycqsjmx9hg3.fsf@multics.mit.edu> (raw)
In-Reply-To: 20050317162613.756101BB98@citi.umich.edu


Chuck Lever <cel <at> citi.umich.edu> writes:

> Create a new file under /proc/self, called mountstats, where mounted file
> systems can export information (configuration options, performance counters,
> and so on). Use a mechanism similar to /proc/mounts and s_ops->show_options.

I'm using this file to dump data into our performance metrics database along
with all the other counters from snmp and other sources. This lets us
calculate things like the average number of requests pending, average latency
per request over time.

But I have a few questions about the meaning of the values and they don't seem
to be documented outside the comments in the source. 

In particular is it an invariant that execution = rtt + queue? Or is execution
including some additional overhead other than the server and network
congestion? Or is there something more subtle going on and these values aren't
related in the way I'm imagining at all?

And where can I read about the meaning of bad_xids, req_u, and bklog_u? What
do they mean?

Also, connect_time, idle_time, req_u, and bklog_u are instantaneous samples
("guages" so to speak), not integrated over time right? So they can't be used
to calculate any aggregates?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-10-13 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 16:26 [PATCH 1/2] VFS: New /proc file /proc/self/mountstats Chuck Lever
2011-10-13 12:58 ` stark-DPNOqEs/LNQ [this message]

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=ycqsjmx9hg3.fsf@multics.mit.edu \
    --to=stark-dpnoqes/lnq@public.gmane.org \
    --cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).