From: Wu Fengguang <fengguang.wu@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "greg@kroah.com" <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/3] DEBUGFS: Add per cpu counters
Date: Tue, 6 Dec 2011 19:44:38 +0800 [thread overview]
Message-ID: <20111206114438.GA17186@localhost> (raw)
In-Reply-To: <1322851407-17182-3-git-send-email-andi@firstfloor.org>
On Sat, Dec 03, 2011 at 02:43:26AM +0800, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> Add a simple way to export per cpu counters in debugfs.
>
> This is done using a section, so that they can be declared using
> a simple macro with minimal typing.
>
> OPEN: modules are not supported yet.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
> fs/debugfs/Makefile | 2 +-
> fs/debugfs/counter.c | 73 +++++++++++++++++++++++++++++++++++++
> include/asm-generic/vmlinux.lds.h | 6 +++
> include/linux/debugfs.h | 27 ++++++++++++++
> 4 files changed, 107 insertions(+), 1 deletions(-)
> create mode 100644 fs/debugfs/counter.c
>
> diff --git a/fs/debugfs/Makefile b/fs/debugfs/Makefile
> index 840c456..21be8d3 100644
> --- a/fs/debugfs/Makefile
> +++ b/fs/debugfs/Makefile
> @@ -1,4 +1,4 @@
> -debugfs-objs := inode.o file.o
> +debugfs-objs := inode.o file.o counter.o
>
> obj-$(CONFIG_DEBUG_FS) += debugfs.o
>
> diff --git a/fs/debugfs/counter.c b/fs/debugfs/counter.c
> new file mode 100644
> index 0000000..2372faf
> --- /dev/null
> +++ b/fs/debugfs/counter.c
> @@ -0,0 +1,73 @@
> +#include <linux/debugfs.h>
> +#include <linux/seq_file.h>
> +#include <linux/percpu.h>
> +#include <linux/kernel.h>
> +
> +/* OPEN: implement module support */
Yeah, I think the module support would benefit my case as well.
To support module users, init_counters() will be exported with the
__start___debugfs/__stop___debugfs hard coding removed. Then I'll be
call it from the readahead initilization code:
DEFINE_PER_CPU(unsigned long[RA_PATTERN_MAX][RA_ACCOUNT_MAX], ra_counter);
struct debugfs_counter ra_pcpu_counter[RA_PATTERN_MAX][RA_ACCOUNT_MAX];
// init ra_pcpu_counter in a loop
for each pattern
init_counters(ra_pcpu_counter[pattern], ra_pcpu_counter[pattern+1]);
Does this usage sound reasonable?
> +extern struct debugfs_counter __start___debugfs[], __stop___debugfs[];
> +
> +static unsigned sum_counter(unsigned __percpu *counter)
> +{
> + int cpu;
> + unsigned sum = 0;
> +
> + for_each_online_cpu (cpu)
> + sum += per_cpu(*counter, cpu);
> + return sum;
> +}
> +
> +static int
> +dump_counters(struct seq_file *m,
> + struct debugfs_counter *cnt, struct debugfs_counter *stop,
> + char *fn)
> +{
> + int n = 0;
> + for (; cnt < stop; cnt++)
> + if (fn[0] == cnt->fn[0] && !strcmp(cnt->fn, fn))
> + n += seq_printf(m, "%s: %u\n",
> + cnt->name, sum_counter(cnt->ptr));
> + return n;
> +}
> +
> +static int show_debugfs_counter(struct seq_file *m, void *arg)
> +{
> + int n;
> + n = dump_counters(m, __start___debugfs, __stop___debugfs, m->private);
That hard coded __start___debugfs/__stop___debugfs is OK for POC, and
will need to be improved to work with multiple users in kernel.
Thanks,
Fengguang
next prev parent reply other threads:[~2011-12-06 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 18:43 Add simple way to add statistic counters to debugfs Andi Kleen
2011-12-02 18:43 ` [PATCH 1/3] DEBUGFS: Automatically create parents for debugfs files Andi Kleen
2011-12-02 19:17 ` Greg KH
2011-12-02 19:42 ` Andi Kleen
2011-12-02 19:58 ` Greg KH
2011-12-02 18:43 ` [PATCH 2/3] DEBUGFS: Add per cpu counters Andi Kleen
2011-12-06 11:44 ` Wu Fengguang [this message]
2011-12-06 17:17 ` Andi Kleen
2011-12-09 3:00 ` Wu Fengguang
2011-12-02 18:43 ` [PATCH 3/3] VFS: Add event counting to dcache Andi Kleen
2011-12-02 19:18 ` Add simple way to add statistic counters to debugfs Greg KH
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=20111206114438.GA17186@localhost \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).