From: Namjae Jeon <linkinjeon@gmail.com>
To: jaegeuk.kim@samsung.com, rostedt@goodmis.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Namjae Jeon <linkinjeon@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
Pankaj Kumar <pankaj.km@samsung.com>
Subject: [PATCH v4 4/7] f2fs: add tracepoints for GC threads
Date: Sat, 20 Apr 2013 01:29:18 +0900 [thread overview]
Message-ID: <1366388958-18915-1-git-send-email-linkinjeon@gmail.com> (raw)
From: Namjae Jeon <namjae.jeon@samsung.com>
Add tracepoints for tracing the garbage collector
threads in f2fs with status of collection & type.
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Signed-off-by: Pankaj Kumar <pankaj.km@samsung.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
---
fs/f2fs/gc.c | 2 ++
include/trace/events/f2fs.h | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 40 insertions(+)
diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
index 37b05e1..935ca8c 100644
--- a/fs/f2fs/gc.c
+++ b/fs/f2fs/gc.c
@@ -23,6 +23,7 @@
#include "node.h"
#include "segment.h"
#include "gc.h"
+#include <trace/events/f2fs.h>
static struct kmem_cache *winode_slab;
@@ -304,6 +305,7 @@ got_it:
}
mutex_unlock(&dirty_i->seglist_lock);
+ trace_f2fs_get_victim(sbi->sb, gc_type, type, &p, sbi->cur_victim_sec);
return (p.min_segno == NULL_SEGNO) ? 0 : 1;
}
diff --git a/include/trace/events/f2fs.h b/include/trace/events/f2fs.h
index c7e71f9..57b6487 100644
--- a/include/trace/events/f2fs.h
+++ b/include/trace/events/f2fs.h
@@ -6,6 +6,7 @@
#include <linux/tracepoint.h>
+struct victim_sel_policy;
TRACE_EVENT(f2fs_sync_file_enter,
TP_PROTO(struct file *file, char advise, int datasync),
@@ -471,6 +472,43 @@ TRACE_EVENT(f2fs_get_data_block,
(unsigned long long) __entry->bh_block,
__entry->size, __entry->ret)
);
+
+TRACE_EVENT(f2fs_get_victim,
+ TP_PROTO(struct super_block *sb, int gc_type, int type,
+ struct victim_sel_policy *p, unsigned int victim),
+
+ TP_ARGS(sb, gc_type, type, p, victim),
+
+ TP_STRUCT__entry(
+ __field(dev_t, dev)
+ __field(int, gc_type)
+ __field(int, type)
+ __field(int, alloc_mode)
+ __field(int, gc_mode)
+ __field(unsigned int, ofs_unit)
+ __field(unsigned int, min_segno)
+ __field(unsigned int, victim)
+ ),
+
+ TP_fast_assign(
+ __entry->dev = sb->s_dev;
+ __entry->gc_type = gc_type;
+ __entry->type = type;
+ __entry->alloc_mode = p->alloc_mode;
+ __entry->gc_mode = p->gc_mode;
+ __entry->ofs_unit = p->ofs_unit;
+ __entry->min_segno = p->min_segno;
+ __entry->victim = victim;
+ ),
+
+ TP_printk("dev %d,%d GC_type %d Data type %d Alloc_mode %d Gc_mode %d "
+ "Bitmap %u Segment No %u Victim %u" ,
+ MAJOR(__entry->dev), MINOR(__entry->dev),
+ __entry->gc_type, __entry->type, __entry->alloc_mode,
+ __entry->gc_mode, __entry->ofs_unit, __entry->min_segno,
+ __entry->victim)
+);
+
#endif /* _TRACE_F2FS_H */
/* This part must be outside protection */
--
1.7.9.5
next reply other threads:[~2013-04-19 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 16:29 Namjae Jeon [this message]
2013-04-23 10:39 ` [PATCH v4 4/7] f2fs: add tracepoints for GC threads Jaegeuk Kim
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=1366388958-18915-1-git-send-email-linkinjeon@gmail.com \
--to=linkinjeon@gmail.com \
--cc=jaegeuk.kim@samsung.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=pankaj.km@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).