From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>,
npiggin@kernel.dk, tim.c.chen@intel.com
Subject: Re: [PATCH] VFS: Add VFS event counter infrastructure
Date: Sun, 22 May 2011 03:21:26 +0100 [thread overview]
Message-ID: <20110522022126.GJ19987@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1305332052-15633-1-git-send-email-andi@firstfloor.org>
On Fri, May 13, 2011 at 05:14:12PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> The recently discovered problem with RCU walks not working for absolute path
> motivated me to add some counters for these events to the VFS. Networking
> and VM has had such counters for a long time and they were always useful
> to diagnose performance problems. An advantage of counters over tracepoints
> is that they are always collected and are low enough overhead that
> they can be always enabled (unlike tracing)
>
> This patch implements a simple per CPU counter framework for the VFS.
> The counters are per CPU and are very little overhead. The counters
> are output in debugfs (/sys/kernel/fs/vfsstat)
WTF? Since when had debugfs become mandatory?
> + fs = debugfs_create_dir("fs", NULL);
> + if (fs)
> + debugfs_create_file("vfsstat", 0444, fs, NULL, &vfsstat_fops);
> + return 0;
Note that if that FPOS is configured away debugfs_create_dir() does _NOT_
return NULL - you get ERR_PTR(-ENODEV).
next prev parent reply other threads:[~2011-05-22 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 0:14 Andi Kleen
2011-05-22 2:21 ` Al Viro [this message]
2011-05-22 2:24 ` Andi Kleen
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=20110522022126.GJ19987@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=tim.c.chen@intel.com \
/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
all inboxes | Powered by JetHome®