All of lore.kernel.org
 help / color / mirror / Atom feed
From: TaoMa <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] ocfs2: add trace event support for ocfs2
Date: Fri, 16 Oct 2009 06:29:00 +0800	[thread overview]
Message-ID: <4AD7A22C.2060706@oracle.com> (raw)
In-Reply-To: <20091015091524.GC14500@mail.oracle.com>

Joel Becker wrote:
> On Thu, Oct 15, 2009 at 11:05:45AM +0800, Tao Ma wrote:
>   
>> Hi Joel/Wengang,
>>
>> Joel Becker wrote:
>>     
>>> On Thu, Sep 17, 2009 at 06:19:44AM +0800, Wengang Wang wrote:
>>>       
>>>> following patches add trace event support for ocfs2.
>>>>         
>>> Wengang,
>>> 	This looks like a nice start.  Thank you for getting this going.
>>> I'm sorry I haven't gotten back until now, I've been busy.
>>> 	What I'd like to do next is get a small starting set of
>>> tracepoints.  You have one tracepoint in this patch as a good example,
>>> but we should get a few more.  I don't want every mlog changed into a
>>> tracepoint.  Some of them are old and useless :-)  Instead, I'd like to
>>> find information we often want while debugging.
>>> 	Tao, Tiger, and Sunil, what are parts of the code you often come
>>> across when debugging?  Certain mlog() prints you always find really
>>> important to see.  If you point them out, Wengang can cook up
>>> tracepoints for them.
>>>       
>> aops.c maybe? And recovery/dlm(The most awesome part)?
>>     
>
> 	But what things?  We're not just going to replace every mlog,
> and we're not going to do every function.  We really want to figure out
> what information is actually useful and add tracepoints for it.  So if
> you have particular functions you need data on, or particular mlog()
> calls you always like to see, we'd love to hear about it.
>   
No idea of recovery/dlm since I don't have much experience in it.
As for aops.c, I think the most important part is ocfs2_write_begin_no_lock.
It is very complicated, sometimes it will write inline_data, sometimes 
CoW a refcount record, sometimes makes a extent written. It is helpful 
for us to know some detail information about it.

Regards,
Tao
> 	Wengang, dlmglue.c is definitely a place to look at.  I'd love
> to see events for the inc/dec of l_ro_holders and l_ex_holders.  I'd
> also love to see the mlogs for 'BAST fired' and 'UNLOCK AST fired'
> converted, and a similar event for the regular AST.
>
> Joel
>
>   

      reply	other threads:[~2009-10-15 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 22:19 [Ocfs2-devel] [PATCH 0/2] ocfs2: add trace event support for ocfs2 Wengang Wang
2009-09-17  7:51 ` Wengang Wang
2009-10-13 20:33 ` Joel Becker
2009-10-14  1:07   ` Wengang Wang
2009-10-15  3:05   ` Tao Ma
2009-10-15  9:15     ` Joel Becker
2009-10-15 22:29       ` TaoMa [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=4AD7A22C.2060706@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.