[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1366388891-18778-1-git-send-email-linkinjeon@gmail.com>
Date: Sat, 20 Apr 2013 01:28:11 +0900
From: Namjae Jeon <linkinjeon@...il.com>
To: jaegeuk.kim@...sung.com, rostedt@...dmis.org
Cc: linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Namjae Jeon <linkinjeon@...il.com>,
Namjae Jeon <namjae.jeon@...sung.com>
Subject: [PATCH v4 0/7] f2fs: Add tracepoints support in f2fs filesystem
From: Namjae Jeon <namjae.jeon@...sung.com>
Add tracepoints in f2fs filesystem for tracing the filesystem
operations for information/debugging purpose if needed. All the
tracepoints are clubbed with respect to functionalities.
Change Log:
v4: Modified the tracepoints as per the review comments of
Jaegeuk Kim. Following tracepoints are added newly:
trace_f2fs_truncate_blocks_enter
trace_f2fs_truncate_blocks_exit
trace_f2fs_truncate_inode_blocks_enter
trace_f2fs_truncate_inode_blocks_exit
trace_f2fs_truncate_node
trace_f2fs_submit_write_page
trace_f2fs_do_submit_bio
trace_f2fs_write_checkpoint
While some of the tracepoints are modified to add new
parameters.
v3: Introduced TRACE_EVENT_CONDITION() macro for checking the
condition page->mapping inside the trace point function call as
per Steve's review comment for the patch
v2: Added DECLARE_EVENT_CLASS() macro for combining the similar
type of trace function calls which has same type of arguments.
v1: Introduced the tracepoint functions in f2fs filesystem.
Namjae Jeon (7):
f2fs: add tracepoints for sync & Inode operations
f2fs: add tracepoints for truncate operation
f2fs: add tracepoint for tracing the page i/o operations
f2fs: add tracepoints for GC threads
f2fs: add tracepoints to debug the block allocation & fallocate
f2fs: add tracepoints for write page operations
f2fs: add tracepoints to debug checkpoint request
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists