All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 5/5] ocfs2: Remove mlog(0) from fs/ocfs2/alloc.c
Date: Wed, 10 Nov 2010 22:39:25 +0800	[thread overview]
Message-ID: <4CDAAE9D.8020102@oracle.com> (raw)
In-Reply-To: <20101110095058.GF31158@mail.oracle.com>

Joel Becker wrote:
> On Wed, Nov 10, 2010 at 10:52:23AM +0800, Tao Ma wrote:
>   
>> So this patch removes all mlog(0,...) from alloc.c and adds
>> the corresponding tracepoints. Different mlogs have different
>> solutions.
>> 1. Some are replaced with trace event directly.
>> 2. Some are replaced and some new parameters are added since
>>    I think we need to know the btree owner in that case.
>> 3. Some are combined into one trace events.
>> 4. Some redundant mlogs are removed.
>>     
>
> 	These decisions are what I stressed to Wengang when he did his
> first pass.  I don't want to log data just because it used to have an
> mlog().  We should only be logging things that are interesting.
>   
yeah, that is also my thought. So I will only change those mlog(0,...) 
that I think I am familar with and
leave others there(I guess I won't touch dlm, cluster and dlmglue).
> 	In this patch, I see a lot of things that make sense.  "Hey,
> we're growing the tree" is a good thing to log.  So I'm not saying that
> you did anything wrong.  I'm just mentioning my goals up front to be
> clear.
> 	Overall, the patch looks good.
>   
Glad to hear that. So I will continue. I guess I can work on most files 
under fs/ocfs2/ except dlmglue.c. ;)
>   
>> What's more, it defines some event classes so that we can use
>> them later.
>>     
>
> 	This is cool.
>   
yeah, they are really cool.

Regards,
Tao

      reply	other threads:[~2010-11-10 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  2:51 [Ocfs2-devel] [PATCH 0/5] The first try of adding trace event to ocfs2 Tao Ma
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 [this message]

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=4CDAAE9D.8020102@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 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.