From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: rostedt@goodmis.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH v4 0/7] f2fs: Add tracepoints support in f2fs filesystem
Date: Tue, 23 Apr 2013 19:37:41 +0900 [thread overview]
Message-ID: <1366713461.31792.9.camel@kjgkr> (raw)
In-Reply-To: <1366388891-18778-1-git-send-email-linkinjeon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1793 bytes --]
Hi, Namjae.
Still I found several inconsistent codes and flaws of information across
the whole patches.
I've finished changing them, so please review the subsequent patches.
Thanks,
2013-04-20 (토), 01:28 +0900, Namjae Jeon:
> From: Namjae Jeon <namjae.jeon@samsung.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
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-23 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 16:28 [PATCH v4 0/7] f2fs: Add tracepoints support in f2fs filesystem Namjae Jeon
2013-04-23 10:37 ` Jaegeuk Kim [this message]
2013-04-23 23:15 ` Namjae Jeon
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=1366713461.31792.9.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linkinjeon@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=rostedt@goodmis.org \
/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).