From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: adds mlogs to aops.c -V3
Date: Mon, 31 Aug 2009 08:51:08 +0800 [thread overview]
Message-ID: <4A9B1E7C.7000304@oracle.com> (raw)
In-Reply-To: <20090828214943.GB29312@mail.oracle.com>
Hi Joel,
Joel Becker wrote:
> On Fri, Aug 28, 2009 at 03:40:21PM +0800, Wengang Wang wrote:
>> Ok. Then I will pick up the mlog_error()s and mlog(ERR...)s and re-post
>> later...
>
> Sounds good.
> If the area of logging interests you, would you take a stab at
> adding tracepoints to ocfs2? Mainline has a generic infrastructure for
> "tracepoints" that can be dropped in nicely in code and don't have to be
> printk()d. Debugfs files can be used to enable them or disable them as
> a group or individually, so we could even just say "only trace
> ocfs2_new_inode". The tracing can be filtered by pid or by function,
> too.
> See Documentation/trace/tracepoints.txt for a little overview,
> but really look at include/trace/events/ext4.h and the associated calls
> in fs/ext4. I'd love to see a small include/trace/events/ocfs2.h to
> start. Maybe just give aio_write and aio_read callers or something.
> Just so there is a nice example for others to follow.
> include/trace/events/o2dlm.h would be cool too, we could trace locking
> calls.
> Feel free to ask me any questions.
>
That sounds very interesting to me!
and will ask you questions inside ocfs2 and outside it :D
regards,
wengang.
next prev parent reply other threads:[~2009-08-31 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 6:02 [Ocfs2-devel] [PATCH] ocfs2: adds mlogs to aops.c -V3 Wengang Wang
2009-08-28 1:10 ` Joel Becker
2009-08-28 2:12 ` Wengang Wang
2009-08-28 5:39 ` Joel Becker
2009-08-28 7:00 ` Wengang Wang
2009-08-28 7:34 ` Joel Becker
2009-08-28 7:40 ` Wengang Wang
2009-08-28 8:14 ` Joel Becker
2009-08-28 21:49 ` Joel Becker
2009-08-31 0:51 ` Wengang Wang [this message]
2009-08-28 7:41 ` Tao Ma
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=4A9B1E7C.7000304@oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.