1. 22 2月, 2011 2 次提交
    • T
      ocfs2: Remove mlog(0) from fs/ocfs2/localalloc.c · a04733d8
      Tao Ma 提交于
      This is the 2nd step to remove the debug info of DISK_ALLOC.
      
      So this patch removes all mlog(0,...) from localalloc.c and adds
      the corresponding tracepoints. Different mlogs have different
      solutions.
      1. Some are replaced with trace event directly.
      2. Some are replaced while some new parameters are added.
      3. Some are combined into one trace events.
      4. Some redundant mlogs are removed.
      Signed-off-by: NTao Ma <boyu.mt@taobao.com>
      a04733d8
    • T
      ocfs2: Remove mlog(0) from fs/ocfs2/alloc.c · a09d09b8
      Tao Ma 提交于
      This is the first try of replacing debug mlog(0,...) to
      trace events. Wengang has did some work in his original
      patch
      http://oss.oracle.com/pipermail/ocfs2-devel/2009-November/005513.html
      But he didn't finished it.
      
      So this patch removes all mlog(0,...) from alloc.c and adds
      the corresponding trace events. 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.
      What's more, it defines some event classes so that we can use
      them later.
      
      Cc: Wengang Wang <wen.gang.wang@oracle.com>
      Signed-off-by: NTao Ma <boyu.mt@taobao.com>
      a09d09b8
  2. 21 2月, 2011 1 次提交
  3. 07 3月, 2011 1 次提交
    • T
      ocfs2: Remove EXIT from masklog. · c1e8d35e
      Tao Ma 提交于
      mlog_exit is used to record the exit status of a function.
      But because it is added in so many functions, if we enable it,
      the system logs get filled up quickly and cause too much I/O.
      So actually no one can open it for a production system or even
      for a test.
      
      This patch just try to remove it or change it. So:
      1. if all the error paths already use mlog_errno, it is just removed.
         Otherwise, it will be replaced by mlog_errno.
      2. if it is used to print some return value, it is replaced with
         mlog(0,...).
      mlog_exit_ptr is changed to mlog(0.
      All those mlog(0,...) will be replaced with trace events later.
      Signed-off-by: NTao Ma <boyu.mt@taobao.com>
      c1e8d35e
  4. 21 2月, 2011 1 次提交
    • T
      ocfs2: Remove ENTRY from masklog. · ef6b689b
      Tao Ma 提交于
      ENTRY is used to record the entry of a function.
      But because it is added in so many functions, if we enable it,
      the system logs get filled up quickly and cause too much I/O.
      So actually no one can open it for a production system or even
      for a test.
      
      So for mlog_entry_void, we just remove it.
      for mlog_entry(...), we replace it with mlog(0,...), and they
      will be replace by trace event later.
      Signed-off-by: NTao Ma <boyu.mt@taobao.com>
      ef6b689b
  5. 16 3月, 2011 15 次提交
  6. 15 3月, 2011 20 次提交