All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-fsdevel@vger.kernel.org, linux-cifs-client@lists.samba.org
Subject: Re: mountstats
Date: Mon, 14 Aug 2006 13:35:43 -0500	[thread overview]
Message-ID: <44E0C27F.4070304@us.ibm.com> (raw)
In-Reply-To: <1155576129.5664.94.camel@localhost>

Trond Myklebust wrote:

>On Tue, 2006-08-08 at 17:21 -0500, Steve French wrote:
>  
>
>>Why are mountstats per process (e.g. "cat /proc/1/mountstats")?
>>    
>>
>
>Namespaces are per-process, hence so are the per-mountpoint mountstats.
>
>Cheers,
>  Trond
>
>  
>
Namespaces are per process but superblocks are not.  It could be 
confusing to some users. Locating
these stats [only] in the perprocess information (alongside some truly 
per-process stats) creates
the impression that the stats are those I/Os for that per-process for 
that mount while
the stats displayed are the stats for the superblock (across all 
processes that have the superblock
in the namespace).  I realize that it would not really be possible to 
show per-process/per-mount stats
but it seems odd that the per-superblock mountstats show up only here, 
rather in a more intuitive
location(s) such as /proc/mountstats [as well].

  reply	other threads:[~2006-08-14 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 22:21 mountstats Steve French
2006-08-14 17:22 ` mountstats Trond Myklebust
2006-08-14 18:35   ` Steve French (smfltc) [this message]
2006-08-14 18:46     ` mountstats Trond Myklebust

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=44E0C27F.4070304@us.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@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.