2006-03-23 12:00:26 -07:00
|
|
|
#ifndef BLKTRACE_H
|
|
|
|
#define BLKTRACE_H
|
|
|
|
|
|
|
|
#include <linux/blkdev.h>
|
|
|
|
#include <linux/relay.h>
|
2010-07-07 08:51:26 -06:00
|
|
|
#include <linux/compat.h>
|
2012-10-13 03:46:48 -06:00
|
|
|
#include <uapi/linux/blktrace_api.h>
|
2013-09-17 14:30:31 -06:00
|
|
|
#include <linux/list.h>
|
2008-09-26 02:58:02 -06:00
|
|
|
|
|
|
|
#if defined(CONFIG_BLK_DEV_IO_TRACE)
|
2009-01-26 10:00:56 -07:00
|
|
|
|
|
|
|
#include <linux/sysfs.h>
|
|
|
|
|
2006-03-23 12:00:26 -07:00
|
|
|
struct blk_trace {
|
|
|
|
int trace_state;
|
|
|
|
struct rchan *rchan;
|
2010-02-01 22:38:57 -07:00
|
|
|
unsigned long __percpu *sequence;
|
|
|
|
unsigned char __percpu *msg_data;
|
2006-03-23 12:00:26 -07:00
|
|
|
u16 act_mask;
|
|
|
|
u64 start_lba;
|
|
|
|
u64 end_lba;
|
|
|
|
u32 pid;
|
|
|
|
u32 dev;
|
|
|
|
struct dentry *dir;
|
|
|
|
struct dentry *dropped_file;
|
2008-06-11 01:12:52 -06:00
|
|
|
struct dentry *msg_file;
|
2013-09-17 14:30:31 -06:00
|
|
|
struct list_head running_list;
|
2006-03-23 12:00:26 -07:00
|
|
|
atomic_t dropped;
|
|
|
|
};
|
|
|
|
|
2017-07-12 12:49:56 -06:00
|
|
|
struct blkcg;
|
|
|
|
|
2006-03-23 12:00:26 -07:00
|
|
|
extern int blk_trace_ioctl(struct block_device *, unsigned, char __user *);
|
2007-07-24 01:28:11 -06:00
|
|
|
extern void blk_trace_shutdown(struct request_queue *);
|
2017-07-12 12:49:56 -06:00
|
|
|
extern __printf(3, 4)
|
|
|
|
void __trace_note_message(struct blk_trace *, struct blkcg *blkcg, const char *fmt, ...);
|
2007-10-09 05:23:53 -06:00
|
|
|
|
2008-05-27 06:54:41 -06:00
|
|
|
/**
|
|
|
|
* blk_add_trace_msg - Add a (simple) message to the blktrace stream
|
|
|
|
* @q: queue the io is for
|
|
|
|
* @fmt: format to print message in
|
|
|
|
* args... Variable argument list for format
|
|
|
|
*
|
|
|
|
* Description:
|
|
|
|
* Records a (simple) message onto the blktrace stream.
|
|
|
|
*
|
|
|
|
* NOTE: BLK_TN_MAX_MSG characters are output at most.
|
|
|
|
* NOTE: Can not use 'static inline' due to presence of var args...
|
|
|
|
*
|
|
|
|
**/
|
2017-07-12 12:49:56 -06:00
|
|
|
#define blk_add_cgroup_trace_msg(q, cg, fmt, ...) \
|
2008-05-27 06:54:41 -06:00
|
|
|
do { \
|
|
|
|
struct blk_trace *bt = (q)->blk_trace; \
|
|
|
|
if (unlikely(bt)) \
|
2017-07-12 12:49:56 -06:00
|
|
|
__trace_note_message(bt, cg, fmt, ##__VA_ARGS__);\
|
2008-05-27 06:54:41 -06:00
|
|
|
} while (0)
|
2017-07-12 12:49:56 -06:00
|
|
|
#define blk_add_trace_msg(q, fmt, ...) \
|
|
|
|
blk_add_cgroup_trace_msg(q, NULL, fmt, ##__VA_ARGS__)
|
2008-05-28 06:45:33 -06:00
|
|
|
#define BLK_TN_MAX_MSG 128
|
2006-03-23 12:00:26 -07:00
|
|
|
|
2016-05-09 18:22:15 -06:00
|
|
|
static inline bool blk_trace_note_message_enabled(struct request_queue *q)
|
|
|
|
{
|
|
|
|
struct blk_trace *bt = q->blk_trace;
|
|
|
|
if (likely(!bt))
|
|
|
|
return false;
|
|
|
|
return bt->act_mask & BLK_TC_NOTIFY;
|
|
|
|
}
|
|
|
|
|
2008-10-30 01:34:33 -06:00
|
|
|
extern void blk_add_driver_data(struct request_queue *q, struct request *rq,
|
|
|
|
void *data, size_t len);
|
2008-01-29 11:12:06 -07:00
|
|
|
extern int blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
|
2009-04-13 23:58:56 -06:00
|
|
|
struct block_device *bdev,
|
2008-01-11 02:09:43 -07:00
|
|
|
char __user *arg);
|
2008-01-29 11:12:06 -07:00
|
|
|
extern int blk_trace_startstop(struct request_queue *q, int start);
|
|
|
|
extern int blk_trace_remove(struct request_queue *q);
|
2009-09-24 22:19:26 -06:00
|
|
|
extern void blk_trace_remove_sysfs(struct device *dev);
|
2009-04-14 00:00:05 -06:00
|
|
|
extern int blk_trace_init_sysfs(struct device *dev);
|
2008-01-11 02:09:43 -07:00
|
|
|
|
2009-01-26 10:00:56 -07:00
|
|
|
extern struct attribute_group blk_trace_attr_group;
|
|
|
|
|
2006-03-23 12:00:26 -07:00
|
|
|
#else /* !CONFIG_BLK_DEV_IO_TRACE */
|
2009-04-13 23:58:56 -06:00
|
|
|
# define blk_trace_ioctl(bdev, cmd, arg) (-ENOTTY)
|
|
|
|
# define blk_trace_shutdown(q) do { } while (0)
|
|
|
|
# define blk_add_driver_data(q, rq, data, len) do {} while (0)
|
|
|
|
# define blk_trace_setup(q, name, dev, bdev, arg) (-ENOTTY)
|
|
|
|
# define blk_trace_startstop(q, start) (-ENOTTY)
|
|
|
|
# define blk_trace_remove(q) (-ENOTTY)
|
|
|
|
# define blk_add_trace_msg(q, fmt, ...) do { } while (0)
|
2017-07-12 12:49:56 -06:00
|
|
|
# define blk_add_cgroup_trace_msg(q, cg, fmt, ...) do { } while (0)
|
2009-10-01 13:16:13 -06:00
|
|
|
# define blk_trace_remove_sysfs(dev) do { } while (0)
|
2016-05-09 18:22:15 -06:00
|
|
|
# define blk_trace_note_message_enabled(q) (false)
|
2009-04-14 00:00:05 -06:00
|
|
|
static inline int blk_trace_init_sysfs(struct device *dev)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-03-23 12:00:26 -07:00
|
|
|
#endif /* CONFIG_BLK_DEV_IO_TRACE */
|
2009-04-13 23:58:56 -06:00
|
|
|
|
2010-07-08 22:24:38 -06:00
|
|
|
#ifdef CONFIG_COMPAT
|
|
|
|
|
|
|
|
struct compat_blk_user_trace_setup {
|
2013-11-03 07:23:39 -07:00
|
|
|
char name[BLKTRACE_BDEV_SIZE];
|
2010-07-08 22:24:38 -06:00
|
|
|
u16 act_mask;
|
|
|
|
u32 buf_size;
|
|
|
|
u32 buf_nr;
|
|
|
|
compat_u64 start_lba;
|
|
|
|
compat_u64 end_lba;
|
|
|
|
u32 pid;
|
|
|
|
};
|
|
|
|
#define BLKTRACESETUP32 _IOWR(0x12, 115, struct compat_blk_user_trace_setup)
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2017-01-27 01:35:54 -07:00
|
|
|
extern void blk_fill_rwbs(char *rwbs, unsigned int op, int bytes);
|
tracing/events: convert block trace points to TRACE_EVENT()
TRACE_EVENT is a more generic way to define tracepoints. Doing so adds
these new capabilities to this tracepoint:
- zero-copy and per-cpu splice() tracing
- binary tracing without printf overhead
- structured logging records exposed under /debug/tracing/events
- trace events embedded in function tracer output and other plugins
- user-defined, per tracepoint filter expressions
...
Cons:
- no dev_t info for the output of plug, unplug_timer and unplug_io events.
no dev_t info for getrq and sleeprq events if bio == NULL.
no dev_t info for rq_abort,...,rq_requeue events if rq->rq_disk == NULL.
This is mainly because we can't get the deivce from a request queue.
But this may change in the future.
- A packet command is converted to a string in TP_assign, not TP_print.
While blktrace do the convertion just before output.
Since pc requests should be rather rare, this is not a big issue.
- In blktrace, an event can have 2 different print formats, but a TRACE_EVENT
has a unique format, which means we have some unused data in a trace entry.
The overhead is minimized by using __dynamic_array() instead of __array().
I've benchmarked the ioctl blktrace vs the splice based TRACE_EVENT tracing:
dd dd + ioctl blktrace dd + TRACE_EVENT (splice)
1 7.36s, 42.7 MB/s 7.50s, 42.0 MB/s 7.41s, 42.5 MB/s
2 7.43s, 42.3 MB/s 7.48s, 42.1 MB/s 7.43s, 42.4 MB/s
3 7.38s, 42.6 MB/s 7.45s, 42.2 MB/s 7.41s, 42.5 MB/s
So the overhead of tracing is very small, and no regression when using
those trace events vs blktrace.
And the binary output of TRACE_EVENT is much smaller than blktrace:
# ls -l -h
-rw-r--r-- 1 root root 8.8M 06-09 13:24 sda.blktrace.0
-rw-r--r-- 1 root root 195K 06-09 13:24 sda.blktrace.1
-rw-r--r-- 1 root root 2.7M 06-09 13:25 trace_splice.out
Following are some comparisons between TRACE_EVENT and blktrace:
plug:
kjournald-480 [000] 303.084981: block_plug: [kjournald]
kjournald-480 [000] 303.084981: 8,0 P N [kjournald]
unplug_io:
kblockd/0-118 [000] 300.052973: block_unplug_io: [kblockd/0] 1
kblockd/0-118 [000] 300.052974: 8,0 U N [kblockd/0] 1
remap:
kjournald-480 [000] 303.085042: block_remap: 8,0 W 102736992 + 8 <- (8,8) 33384
kjournald-480 [000] 303.085043: 8,0 A W 102736992 + 8 <- (8,8) 33384
bio_backmerge:
kjournald-480 [000] 303.085086: block_bio_backmerge: 8,0 W 102737032 + 8 [kjournald]
kjournald-480 [000] 303.085086: 8,0 M W 102737032 + 8 [kjournald]
getrq:
kjournald-480 [000] 303.084974: block_getrq: 8,0 W 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084975: 8,0 G W 102736984 + 8 [kjournald]
bash-2066 [001] 1072.953770: 8,0 G N [bash]
bash-2066 [001] 1072.953773: block_getrq: 0,0 N 0 + 0 [bash]
rq_complete:
konsole-2065 [001] 300.053184: block_rq_complete: 8,0 W () 103669040 + 16 [0]
konsole-2065 [001] 300.053191: 8,0 C W 103669040 + 16 [0]
ksoftirqd/1-7 [001] 1072.953811: 8,0 C N (5a 00 08 00 00 00 00 00 24 00) [0]
ksoftirqd/1-7 [001] 1072.953813: block_rq_complete: 0,0 N (5a 00 08 00 00 00 00 00 24 00) 0 + 0 [0]
rq_insert:
kjournald-480 [000] 303.084985: block_rq_insert: 8,0 W 0 () 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084986: 8,0 I W 102736984 + 8 [kjournald]
Changelog from v2 -> v3:
- use the newly introduced __dynamic_array().
Changelog from v1 -> v2:
- use __string() instead of __array() to minimize the memory required
to store hex dump of rq->cmd().
- support large pc requests.
- add missing blk_fill_rwbs_rq() in block_rq_requeue TRACE_EVENT.
- some cleanups.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4A2DF669.5070905@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-06-08 23:43:05 -06:00
|
|
|
|
2017-01-27 01:35:54 -07:00
|
|
|
static inline sector_t blk_rq_trace_sector(struct request *rq)
|
tracing/events: convert block trace points to TRACE_EVENT()
TRACE_EVENT is a more generic way to define tracepoints. Doing so adds
these new capabilities to this tracepoint:
- zero-copy and per-cpu splice() tracing
- binary tracing without printf overhead
- structured logging records exposed under /debug/tracing/events
- trace events embedded in function tracer output and other plugins
- user-defined, per tracepoint filter expressions
...
Cons:
- no dev_t info for the output of plug, unplug_timer and unplug_io events.
no dev_t info for getrq and sleeprq events if bio == NULL.
no dev_t info for rq_abort,...,rq_requeue events if rq->rq_disk == NULL.
This is mainly because we can't get the deivce from a request queue.
But this may change in the future.
- A packet command is converted to a string in TP_assign, not TP_print.
While blktrace do the convertion just before output.
Since pc requests should be rather rare, this is not a big issue.
- In blktrace, an event can have 2 different print formats, but a TRACE_EVENT
has a unique format, which means we have some unused data in a trace entry.
The overhead is minimized by using __dynamic_array() instead of __array().
I've benchmarked the ioctl blktrace vs the splice based TRACE_EVENT tracing:
dd dd + ioctl blktrace dd + TRACE_EVENT (splice)
1 7.36s, 42.7 MB/s 7.50s, 42.0 MB/s 7.41s, 42.5 MB/s
2 7.43s, 42.3 MB/s 7.48s, 42.1 MB/s 7.43s, 42.4 MB/s
3 7.38s, 42.6 MB/s 7.45s, 42.2 MB/s 7.41s, 42.5 MB/s
So the overhead of tracing is very small, and no regression when using
those trace events vs blktrace.
And the binary output of TRACE_EVENT is much smaller than blktrace:
# ls -l -h
-rw-r--r-- 1 root root 8.8M 06-09 13:24 sda.blktrace.0
-rw-r--r-- 1 root root 195K 06-09 13:24 sda.blktrace.1
-rw-r--r-- 1 root root 2.7M 06-09 13:25 trace_splice.out
Following are some comparisons between TRACE_EVENT and blktrace:
plug:
kjournald-480 [000] 303.084981: block_plug: [kjournald]
kjournald-480 [000] 303.084981: 8,0 P N [kjournald]
unplug_io:
kblockd/0-118 [000] 300.052973: block_unplug_io: [kblockd/0] 1
kblockd/0-118 [000] 300.052974: 8,0 U N [kblockd/0] 1
remap:
kjournald-480 [000] 303.085042: block_remap: 8,0 W 102736992 + 8 <- (8,8) 33384
kjournald-480 [000] 303.085043: 8,0 A W 102736992 + 8 <- (8,8) 33384
bio_backmerge:
kjournald-480 [000] 303.085086: block_bio_backmerge: 8,0 W 102737032 + 8 [kjournald]
kjournald-480 [000] 303.085086: 8,0 M W 102737032 + 8 [kjournald]
getrq:
kjournald-480 [000] 303.084974: block_getrq: 8,0 W 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084975: 8,0 G W 102736984 + 8 [kjournald]
bash-2066 [001] 1072.953770: 8,0 G N [bash]
bash-2066 [001] 1072.953773: block_getrq: 0,0 N 0 + 0 [bash]
rq_complete:
konsole-2065 [001] 300.053184: block_rq_complete: 8,0 W () 103669040 + 16 [0]
konsole-2065 [001] 300.053191: 8,0 C W 103669040 + 16 [0]
ksoftirqd/1-7 [001] 1072.953811: 8,0 C N (5a 00 08 00 00 00 00 00 24 00) [0]
ksoftirqd/1-7 [001] 1072.953813: block_rq_complete: 0,0 N (5a 00 08 00 00 00 00 00 24 00) 0 + 0 [0]
rq_insert:
kjournald-480 [000] 303.084985: block_rq_insert: 8,0 W 0 () 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084986: 8,0 I W 102736984 + 8 [kjournald]
Changelog from v2 -> v3:
- use the newly introduced __dynamic_array().
Changelog from v1 -> v2:
- use __string() instead of __array() to minimize the memory required
to store hex dump of rq->cmd().
- support large pc requests.
- add missing blk_fill_rwbs_rq() in block_rq_requeue TRACE_EVENT.
- some cleanups.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4A2DF669.5070905@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-06-08 23:43:05 -06:00
|
|
|
{
|
2017-01-31 08:57:29 -07:00
|
|
|
return blk_rq_is_passthrough(rq) ? 0 : blk_rq_pos(rq);
|
tracing/events: convert block trace points to TRACE_EVENT()
TRACE_EVENT is a more generic way to define tracepoints. Doing so adds
these new capabilities to this tracepoint:
- zero-copy and per-cpu splice() tracing
- binary tracing without printf overhead
- structured logging records exposed under /debug/tracing/events
- trace events embedded in function tracer output and other plugins
- user-defined, per tracepoint filter expressions
...
Cons:
- no dev_t info for the output of plug, unplug_timer and unplug_io events.
no dev_t info for getrq and sleeprq events if bio == NULL.
no dev_t info for rq_abort,...,rq_requeue events if rq->rq_disk == NULL.
This is mainly because we can't get the deivce from a request queue.
But this may change in the future.
- A packet command is converted to a string in TP_assign, not TP_print.
While blktrace do the convertion just before output.
Since pc requests should be rather rare, this is not a big issue.
- In blktrace, an event can have 2 different print formats, but a TRACE_EVENT
has a unique format, which means we have some unused data in a trace entry.
The overhead is minimized by using __dynamic_array() instead of __array().
I've benchmarked the ioctl blktrace vs the splice based TRACE_EVENT tracing:
dd dd + ioctl blktrace dd + TRACE_EVENT (splice)
1 7.36s, 42.7 MB/s 7.50s, 42.0 MB/s 7.41s, 42.5 MB/s
2 7.43s, 42.3 MB/s 7.48s, 42.1 MB/s 7.43s, 42.4 MB/s
3 7.38s, 42.6 MB/s 7.45s, 42.2 MB/s 7.41s, 42.5 MB/s
So the overhead of tracing is very small, and no regression when using
those trace events vs blktrace.
And the binary output of TRACE_EVENT is much smaller than blktrace:
# ls -l -h
-rw-r--r-- 1 root root 8.8M 06-09 13:24 sda.blktrace.0
-rw-r--r-- 1 root root 195K 06-09 13:24 sda.blktrace.1
-rw-r--r-- 1 root root 2.7M 06-09 13:25 trace_splice.out
Following are some comparisons between TRACE_EVENT and blktrace:
plug:
kjournald-480 [000] 303.084981: block_plug: [kjournald]
kjournald-480 [000] 303.084981: 8,0 P N [kjournald]
unplug_io:
kblockd/0-118 [000] 300.052973: block_unplug_io: [kblockd/0] 1
kblockd/0-118 [000] 300.052974: 8,0 U N [kblockd/0] 1
remap:
kjournald-480 [000] 303.085042: block_remap: 8,0 W 102736992 + 8 <- (8,8) 33384
kjournald-480 [000] 303.085043: 8,0 A W 102736992 + 8 <- (8,8) 33384
bio_backmerge:
kjournald-480 [000] 303.085086: block_bio_backmerge: 8,0 W 102737032 + 8 [kjournald]
kjournald-480 [000] 303.085086: 8,0 M W 102737032 + 8 [kjournald]
getrq:
kjournald-480 [000] 303.084974: block_getrq: 8,0 W 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084975: 8,0 G W 102736984 + 8 [kjournald]
bash-2066 [001] 1072.953770: 8,0 G N [bash]
bash-2066 [001] 1072.953773: block_getrq: 0,0 N 0 + 0 [bash]
rq_complete:
konsole-2065 [001] 300.053184: block_rq_complete: 8,0 W () 103669040 + 16 [0]
konsole-2065 [001] 300.053191: 8,0 C W 103669040 + 16 [0]
ksoftirqd/1-7 [001] 1072.953811: 8,0 C N (5a 00 08 00 00 00 00 00 24 00) [0]
ksoftirqd/1-7 [001] 1072.953813: block_rq_complete: 0,0 N (5a 00 08 00 00 00 00 00 24 00) 0 + 0 [0]
rq_insert:
kjournald-480 [000] 303.084985: block_rq_insert: 8,0 W 0 () 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084986: 8,0 I W 102736984 + 8 [kjournald]
Changelog from v2 -> v3:
- use the newly introduced __dynamic_array().
Changelog from v1 -> v2:
- use __string() instead of __array() to minimize the memory required
to store hex dump of rq->cmd().
- support large pc requests.
- add missing blk_fill_rwbs_rq() in block_rq_requeue TRACE_EVENT.
- some cleanups.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4A2DF669.5070905@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-06-08 23:43:05 -06:00
|
|
|
}
|
|
|
|
|
2017-01-27 01:35:54 -07:00
|
|
|
static inline unsigned int blk_rq_trace_nr_sectors(struct request *rq)
|
|
|
|
{
|
2017-01-31 08:57:29 -07:00
|
|
|
return blk_rq_is_passthrough(rq) ? 0 : blk_rq_sectors(rq);
|
2017-01-27 01:35:54 -07:00
|
|
|
}
|
tracing/events: convert block trace points to TRACE_EVENT()
TRACE_EVENT is a more generic way to define tracepoints. Doing so adds
these new capabilities to this tracepoint:
- zero-copy and per-cpu splice() tracing
- binary tracing without printf overhead
- structured logging records exposed under /debug/tracing/events
- trace events embedded in function tracer output and other plugins
- user-defined, per tracepoint filter expressions
...
Cons:
- no dev_t info for the output of plug, unplug_timer and unplug_io events.
no dev_t info for getrq and sleeprq events if bio == NULL.
no dev_t info for rq_abort,...,rq_requeue events if rq->rq_disk == NULL.
This is mainly because we can't get the deivce from a request queue.
But this may change in the future.
- A packet command is converted to a string in TP_assign, not TP_print.
While blktrace do the convertion just before output.
Since pc requests should be rather rare, this is not a big issue.
- In blktrace, an event can have 2 different print formats, but a TRACE_EVENT
has a unique format, which means we have some unused data in a trace entry.
The overhead is minimized by using __dynamic_array() instead of __array().
I've benchmarked the ioctl blktrace vs the splice based TRACE_EVENT tracing:
dd dd + ioctl blktrace dd + TRACE_EVENT (splice)
1 7.36s, 42.7 MB/s 7.50s, 42.0 MB/s 7.41s, 42.5 MB/s
2 7.43s, 42.3 MB/s 7.48s, 42.1 MB/s 7.43s, 42.4 MB/s
3 7.38s, 42.6 MB/s 7.45s, 42.2 MB/s 7.41s, 42.5 MB/s
So the overhead of tracing is very small, and no regression when using
those trace events vs blktrace.
And the binary output of TRACE_EVENT is much smaller than blktrace:
# ls -l -h
-rw-r--r-- 1 root root 8.8M 06-09 13:24 sda.blktrace.0
-rw-r--r-- 1 root root 195K 06-09 13:24 sda.blktrace.1
-rw-r--r-- 1 root root 2.7M 06-09 13:25 trace_splice.out
Following are some comparisons between TRACE_EVENT and blktrace:
plug:
kjournald-480 [000] 303.084981: block_plug: [kjournald]
kjournald-480 [000] 303.084981: 8,0 P N [kjournald]
unplug_io:
kblockd/0-118 [000] 300.052973: block_unplug_io: [kblockd/0] 1
kblockd/0-118 [000] 300.052974: 8,0 U N [kblockd/0] 1
remap:
kjournald-480 [000] 303.085042: block_remap: 8,0 W 102736992 + 8 <- (8,8) 33384
kjournald-480 [000] 303.085043: 8,0 A W 102736992 + 8 <- (8,8) 33384
bio_backmerge:
kjournald-480 [000] 303.085086: block_bio_backmerge: 8,0 W 102737032 + 8 [kjournald]
kjournald-480 [000] 303.085086: 8,0 M W 102737032 + 8 [kjournald]
getrq:
kjournald-480 [000] 303.084974: block_getrq: 8,0 W 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084975: 8,0 G W 102736984 + 8 [kjournald]
bash-2066 [001] 1072.953770: 8,0 G N [bash]
bash-2066 [001] 1072.953773: block_getrq: 0,0 N 0 + 0 [bash]
rq_complete:
konsole-2065 [001] 300.053184: block_rq_complete: 8,0 W () 103669040 + 16 [0]
konsole-2065 [001] 300.053191: 8,0 C W 103669040 + 16 [0]
ksoftirqd/1-7 [001] 1072.953811: 8,0 C N (5a 00 08 00 00 00 00 00 24 00) [0]
ksoftirqd/1-7 [001] 1072.953813: block_rq_complete: 0,0 N (5a 00 08 00 00 00 00 00 24 00) 0 + 0 [0]
rq_insert:
kjournald-480 [000] 303.084985: block_rq_insert: 8,0 W 0 () 102736984 + 8 [kjournald]
kjournald-480 [000] 303.084986: 8,0 I W 102736984 + 8 [kjournald]
Changelog from v2 -> v3:
- use the newly introduced __dynamic_array().
Changelog from v1 -> v2:
- use __string() instead of __array() to minimize the memory required
to store hex dump of rq->cmd().
- support large pc requests.
- add missing blk_fill_rwbs_rq() in block_rq_requeue TRACE_EVENT.
- some cleanups.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4A2DF669.5070905@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-06-08 23:43:05 -06:00
|
|
|
|
2006-03-23 12:00:26 -07:00
|
|
|
#endif
|