From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/5] The first try of adding trace event to ocfs2.
Date: Wed, 10 Nov 2010 10:51:34 +0800 [thread overview]
Message-ID: <4CDA08B6.2070002@oracle.com> (raw)
Hi all,
This patch set is my first try to add trace event to ocfs2.
Wengang Wang has did some work in this field about one year ago.
http://oss.oracle.com/pipermail/ocfs2-devel/2009-September/005230.html
But at that time we don't have ocfs2 1.6 introduced, so we delay this
work until now after ocfs2 1.6 and UEK(Unbreakable Enterprise Kernel)
are released.
Patch 1 is actually a clean up and unrelated to trace event, but if we
don't have this one, patch 2/3/4/5 won't be applied cleanly, so I'd like
to include it here.
Patch 2 and 3 are my attempt to remove ML_ENTRY and ML_EXIT. These 2
flags are overused and actually enabling them means disasters in our
debugging.
Patch 4/5 are the real patches for trace event. Please review these 2
patches. And if it is ok, I will go ahead with other files under fs/ocfs2/.
Regards,
Tao
next reply other threads:[~2010-11-10 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 2:51 Tao Ma [this message]
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 1/5] ocfs2: Remove unused truncate function from alloc.c Tao Ma
2010-11-10 9:41 ` Joel Becker
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 2/5] ocfs2: Remove ENTRY from masklog Tao Ma
2010-11-10 9:43 ` Joel Becker
2010-11-10 14:19 ` Tao Ma
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 3/5] ocfs2: Remove EXIT " Tao Ma
2010-11-10 9:45 ` Joel Becker
2010-11-10 14:22 ` Tao Ma
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 4/5] ocfs2: Add ocfs2_trace.h Tao Ma
2010-11-10 9:48 ` Joel Becker
2010-11-10 14:33 ` Tao Ma
2010-11-10 22:19 ` Joel Becker
2010-11-10 2:52 ` [Ocfs2-devel] [PATCH 5/5] ocfs2: Remove mlog(0) from fs/ocfs2/alloc.c Tao Ma
2010-11-10 9:50 ` Joel Becker
2010-11-10 14:39 ` 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=4CDA08B6.2070002@oracle.com \
--to=tao.ma@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 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).