From: Steve French <smfltc@us.ibm.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-cifs-client@lists.samba.org
Subject: mountstats
Date: Tue, 08 Aug 2006 17:21:44 -0500 [thread overview]
Message-ID: <44D90E78.4060006@us.ibm.com> (raw)
Why are mountstats per process (e.g. "cat /proc/1/mountstats")?
The only fs which exports these appears to be nfs. Although it is
probably a good idea to export them for cases like nfs (and cifs and
some clusterfs) by calling show_stats in fs/namespace.c etc. These
stats appear to have nothing to do with per-process data and are rather
per-superblock.
NFS for example shows:
device localhost:/test-share mounted on /mnt with fstype nfs statvers=1.0
opts:
rw,vers=3,rsize=32768,wsize=32768,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,hard,proto=tcp,timeo=600,retrans=3,sec=sys
age: 2436
caps: caps=0x9,wtmult=4096,dtsize=4096,bsize=0,namelen=255
sec: flavor=1,pseudoflavor=1
events: 0 0 0 0 0 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
bytes: 0 0 0 0 0 0 0 0
RPC iostats version: 1.0 p/v: 100003/3 (nfs)
xprt: tcp 721 0 2 0 0 6 6 0 6 0
per-op statistics
NULL: 1 1 0 44 24 0 0 0
GETATTR: 1 1 0 100 112 0 0 0
SETATTR: 0 0 0 0 0 0 0 0
LOOKUP: 1 1 0 128 116 0 0 0
ACCESS: 1 1 0 112 120 0 0 0
READLINK: 0 0 0 0 0 0 0 0
READ: 0 0 0 0 0 0 0 0
WRITE: 0 0 0 0 0 0 0 0
CREATE: 0 0 0 0 0 0 0 0
MKDIR: 0 0 0 0 0 0 0 0
SYMLINK: 0 0 0 0 0 0 0 0
MKNOD: 0 0 0 0 0 0 0 0
REMOVE: 0 0 0 0 0 0 0 0
RMDIR: 0 0 0 0 0 0 0 0
RENAME: 0 0 0 0 0 0 0 0
LINK: 0 0 0 0 0 0 0 0
READDIR: 0 0 0 0 0 0 0 0
READDIRPLUS: 0 0 0 0 0 0 0 0
FSSTAT: 0 0 0 0 0 0 0 0
FSINFO: 1 1 0 100 80 0 4 4
PATHCONF: 0 0 0 0 0 0 0 0
COMMIT: 0 0 0 0 0 0 0 0
Is there another path (other than read of /proc/<pid>/mounstats) which
ends up in s_op->show_stats?
Seems logical to map cifs's /proc/fs/cifs/Stats to this as well as that
already does per-mounted share (close enough to per-mount)
stats including:
SMBs: 6 Oplock Breaks: 0
Reads: 0 Bytes: 0
Writes: 0 Bytes: 0
Locks: 0 HardLinks: 0 Symlinks: 0
Opens: 0 Closes: 0 Deletes: 0
Mkdirs: 0 Rmdirs: 0
Renames: 0 T2 Renames 0
next reply other threads:[~2006-08-08 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 22:21 Steve French [this message]
2006-08-14 17:22 ` mountstats Trond Myklebust
2006-08-14 18:35 ` mountstats Steve French (smfltc)
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=44D90E78.4060006@us.ibm.com \
--to=smfltc@us.ibm.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.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).